Model Context Protocol (MCP)
The Model Context Protocol (MCP) is an open standard that lets AI agents call external tools over HTTP. Dynasend provides two remote MCP servers. Your agent client must support remote HTTP MCP servers (for example Cursor, Claude Code, Claude Desktop, or VS Code).
| Need | Use |
|---|---|
| Search public Dynasend documentation from an agent | Docs search MCP |
| Run authenticated diagnostics against your Dynasend account | Diagnostics MCP |
Docs search MCP
Use the docs search MCP server to let an AI agent search public Dynasend documentation. Access is read-only. Your MCP client does not require a Dynasend account or API key.
Before you begin
- An MCP client that supports remote HTTP MCP servers, such as Cursor, Claude Code, Claude Desktop, or VS Code.
- Network access to the Algolia-hosted MCP URL below.
Endpoint
https://NWWFCENHA0.algolia.net/mcp/1/ZvPJ87qSRguKi2B9s4D0uQ/mcp
Authentication is not required. If your client asks for an OAuth client ID or client secret, leave those fields empty.
Connect from your MCP client
- Cursor
- Claude Code
- Claude Desktop
- VS Code
- Open Settings → Cursor Settings, then click Tools & MCPs.
- Click Add Custom MCP.
- Paste the following into the
mcp.jsonfile that opens, then save:
{
"mcpServers": {
"dynasend-docs": {
"url": "https://NWWFCENHA0.algolia.net/mcp/1/ZvPJ87qSRguKi2B9s4D0uQ/mcp"
}
}
}
- Enable the dynasend-docs connection from the prompt bar when you start a chat.
You can also add the same configuration to ~/.cursor/mcp.json on macOS and Linux, or to %USERPROFILE%\.cursor\mcp.json on Windows.
- Register the MCP server:
claude mcp add --transport http dynasend-docs https://NWWFCENHA0.algolia.net/mcp/1/ZvPJ87qSRguKi2B9s4D0uQ/mcp
- Start a Claude Code session and confirm the server appears when you run
/mcp.
- Open Connectors settings, click +, then click Add custom connector.
- Set Remote MCP server URL to
https://NWWFCENHA0.algolia.net/mcp/1/ZvPJ87qSRguKi2B9s4D0uQ/mcp. - Set Name to
Dynasend docs. - Leave advanced OAuth fields empty.
- Click Add.
- Enable the connector from the prompt bar.
On Claude Team and Enterprise plans, an organization owner adds the connector from Organization settings → Connectors. Other members then click Connect under Customize → Connectors.
- Open the Command Palette and run
MCP: Add Server. - Select HTTP as the transport.
- Enter the server URL:
https://NWWFCENHA0.algolia.net/mcp/1/ZvPJ87qSRguKi2B9s4D0uQ/mcp
- Set the server ID to
dynasend-docs(or another name you prefer). - Choose Workspace or Global as the target.
Alternatively, add the following to ~/.vscode/mcp.json on macOS and Linux, or to %USERPROFILE%\.vscode\mcp.json on Windows:
{
"servers": {
"dynasend-docs": {
"type": "http",
"url": "https://NWWFCENHA0.algolia.net/mcp/1/ZvPJ87qSRguKi2B9s4D0uQ/mcp"
}
}
}
Try it
After the server is connected, ask your agent a documentation question, for example:
Using Dynasend docs, how do I configure SAML SSO with Entra ID?
Diagnostics MCP
Use the diagnostics MCP server to let an AI agent run authenticated diagnostics against your Dynasend account. Access follows your Dynasend permissions after you complete OAuth.
Before you begin
- A Dynasend account with permission to use diagnostics for your tenant.
- An MCP client that supports remote HTTP MCP servers and OAuth, such as Cursor, Claude Code, Claude Desktop, or VS Code.
- The manage host for your tenant region.
Region endpoints
Use the URL that matches where your Dynasend tenant is hosted:
| Region | Server URL |
|---|---|
| US | https://us-east-2.manage.dynasend.net/mcp/diagnostics |
| EU | https://eu-west-1.manage.dynasend.net/mcp/diagnostics |
If you connect to the wrong region, OAuth may succeed while diagnostics fail or return empty results. Confirm your region with your Dynasend administrator if you are unsure.
Authentication
Diagnostics MCP uses Dynasend OAuth. When you connect from a supported client, the client opens a browser sign-in flow. Sign in with your Dynasend account and grant access when prompted.
You do not need to provide an OAuth client ID or client secret. If your MCP client asks for these fields, leave them empty.
Enable tool approval in your MCP client so you can review tool calls before they run.
Connect from your MCP client
Replace the URL in the examples with your region URL from the region table. The examples use US.
- Cursor
- Claude Code
- Claude Desktop
- VS Code
- Open Settings → Cursor Settings, then click Tools & MCPs.
- Click Add Custom MCP.
- Paste the following into the
mcp.jsonfile that opens, then save:
{
"mcpServers": {
"dynasend-diagnostics": {
"url": "https://us-east-2.manage.dynasend.net/mcp/diagnostics"
}
}
}
- Click Connect, then sign in with Dynasend when prompted.
- Enable the dynasend-diagnostics connection from the prompt bar when you start a chat.
You can also add the same configuration to ~/.cursor/mcp.json on macOS and Linux, or to %USERPROFILE%\.cursor\mcp.json on Windows.
- Register the MCP server (use your region URL):
claude mcp add --transport http dynasend-diagnostics https://us-east-2.manage.dynasend.net/mcp/diagnostics
- Start a Claude Code session and run
/mcp. - Sign in with Dynasend when prompted to authorize the connection.
- Open Connectors settings, click +, then click Add custom connector.
- Set Remote MCP server URL to your region URL (for example
https://us-east-2.manage.dynasend.net/mcp/diagnostics). - Set Name to
Dynasend diagnostics. - Leave advanced OAuth client ID and secret fields empty.
- Click Add, then sign in with Dynasend when prompted.
- Enable the connector from the prompt bar.
On Claude Team and Enterprise plans, an organization owner adds the connector from Organization settings → Connectors. Other members then click Connect under Customize → Connectors and complete their own OAuth sign-in.
- Open the Command Palette and run
MCP: Add Server. - Select HTTP as the transport.
- Enter your region server URL, for example:
https://us-east-2.manage.dynasend.net/mcp/diagnostics
- Set the server ID to
dynasend-diagnostics(or another name you prefer). - Choose Workspace or Global as the target.
- Complete the OAuth sign-in when VS Code prompts you.
Alternatively, add the following to ~/.vscode/mcp.json on macOS and Linux, or to %USERPROFILE%\.vscode\mcp.json on Windows (use your region URL):
{
"servers": {
"dynasend-diagnostics": {
"type": "http",
"url": "https://us-east-2.manage.dynasend.net/mcp/diagnostics"
}
}
}
Capabilities
After you authenticate, the agent can call diagnostics tools scoped to your Dynasend account. Available tools depend on your permissions and the current diagnostics MCP release.
Treat prompts and tool results as tenant data. Do not share OAuth sessions across personal and work accounts on the same machine.
Troubleshooting
| Symptom | What to check |
|---|---|
| OAuth window never opens or is dismissed | Start the connection again from the client and complete sign-in in the browser. |
| Connected but tools fail or return no data | Confirm you used the manage host for your tenant region. |
| Connection blocked on a managed network | Ask your IT administrator to allow *.manage.dynasend.net for your region. |
| Wrong Dynasend account authorized | Sign out of Dynasend in the browser, reconnect the MCP server, and sign in with the correct account. |