MCP: a least-privilege read agent

Download the read-only Node.js client. It discovers allowed tools and calls list_dids, without purchases, forwarding changes or SMS sends.

SetupCopy Anchor Link

1. Use Node.js 24 or later and install @modelcontextprotocol/[email protected] in the example directory.
2. Create a token with dids:read. Add billing:read only for expiry/payments and forwarding:read only for destinations.
3. Set NOVODID_API_TOKEN in a secret manager or private environment file. Never store its value in Git, URLs or shared prompts.
4. Run the file. Server: https://mcp.novodid.com/mcp, Streamable HTTP, Authorization: Bearer.
5. Configure the same address and header in another client. OAuth-only clients do not work with this connection.

Suggested agent instructionCopy Anchor Link

“Read my numbers and fields allowed by this token. Do not change anything, create payments or send SMS. State which tools you used. If access is refused, explain without revealing credentials.”

Discovery respects scopes; old tokens do not gain new permissions automatically. Reconnect after changing permissions. A browser 405 on the endpoint does not mean the documentation is down: configure it in an MCP client.

Extending the automationCopy Anchor Link

Separate read and write tokens. Before purchasing, present a quote and obtain explicit consent; after an uncertain result reuse exactly the same idempotencyKey and payload. One number per order. SMS has no idempotency contract and must not be automatically resent. Telephone forwarding consumes per-minute credit. Account rules and current ownership still apply. See the MCP guide and troubleshooting.