Dialplane by Inlayer

The Device Management Service for Cisco BroadWorks, via MCP and REST.

An MCP server and a REST API for your BroadWorks devices. Create, update, list, and read devices today, with each device’s lines, files, and tags. Users, services, groups, and numbers run through the same API.
Connect any MCP client
Claude
ChatGPT
Copilot
Gemini
Codex
Dialplane device request
Scoped
MCP
AI clients
REST
Any system
Dialplane
Schema validationScoped tokensNormalized JSON
Cisco BroadWorks
Access devices, device files, users on each line
Devices
Phones and gateways
What it does

Device work from an AI client or from any system.

REST for Provisioning Systems

Create and update access devices, read their lines, files, and tags, and list devices at group, service provider, or system level. Send JSON, get normalized JSON back. Dialplane handles OCI-P rendering, parsing, and release-specific commands.

MCP for AI Clients

Ask which users sit on a phone’s lines or which tags a device carries, then let the AI client create or update devices within its token’s scopes. No raw sockets, XML, or unscoped credentials.

The Rest of BroadWorks

The same API provisions users, assigns services and numbers, and configures groups, so a new phone and the user who will use it are created in one session.

What the DMS Covers

The device work BroadWorks teams do every day.

MCP tools and REST workflows create, update, list, and read devices today. Items marked rolling out are on their way as dedicated device tools.

Partly available

Device Types

Every device list and read names the device type.

Rolling out: read each device type and the template files it serves.

Available

Device Profiles

Create an access device of any type at group or service provider level, update its MAC and net address, then list and read it back.

Partly available

Line and Port Assignment

See which user sits on each line and port of a device, and which line is primary.

Rolling out: assign users to lines.

Partly available

Custom Tags and Tag Sets

Read the custom tags and tag set that fill in a device configuration template.

Rolling out: set them.

Partly available

Custom Files

List the files a device serves, with their source and URL.

Rolling out: replace a template file where a device needs its own.

Rolling out

Rebuild and Reset

Rebuild configuration files after a change and reset the device so it picks up the new configuration.

A device change, end to end

Create, check, and update devices from one conversation.

Work from an AI client over MCP, or script the same steps over REST. Dialplane checks each request against the token’s scopes before sending it, and BroadWorks keeps it within what the signed-in login can reach.

01

Create the access device with its type and MAC address

02

List the group’s devices to confirm the new one is there

03

Read the device to see which users are on each line and port

04

Check the custom tags, tag set, and files the device serves

05

Update the MAC or net address when the hardware is swapped

06

Read the device back to confirm the change

Example MCP promptstoken: device-team

    
Tenant access control

Give every client exactly the device reach it needs.

Scoped tokens. Start with full access for fast setup, then narrow by scopes such as read:device, provision:device, or read:user.

Tenant bounds. Limit a token to specific service providers or groups.

Login-tier policy. Set ceilings per BroadWorks login type and inspect recent scope denies.

API tokens
sp-northwind
device-teamActive
read:deviceprovision:deviceread:usergroup: grp-east
inventory-syncActive
read:device
Denied: update device desk-204inventory-sync is missing provision:device.
Built for device teams

Device changes without raw XML or unscoped access.

Dialplane builds BroadWorks commands from typed schemas and returns typed JSON. Passwords sent to BroadWorks are redacted from logs, and deleting a service provider, group, or reseller is never allowed through the API.

Normalized responses

Clean JSON

Typed, camelCase data from BroadWorks OCI responses. Clients never parse XML.

Two interfaces

REST + MCP

Provisioning systems and AI clients use the same tenant-safe device API.

Device credentials

Never returned

A device read reports whether credentials are set, never the device password.

Next steps

Put your BroadWorks device work behind one API.

Start with MCP and REST access for your BroadWorks admin logins, and tell us which device work you want to move first.
Inlayer