Skip to main content

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).

NeedUse
Search public Dynasend documentation from an agentDocs search MCP
Run authenticated diagnostics against your Dynasend accountDiagnostics 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​

  1. Open Settings → Cursor Settings, then click Tools & MCPs.
  2. Click Add Custom MCP.
  3. Paste the following into the mcp.json file that opens, then save:
{
"mcpServers": {
"dynasend-docs": {
"url": "https://NWWFCENHA0.algolia.net/mcp/1/ZvPJ87qSRguKi2B9s4D0uQ/mcp"
}
}
}
  1. 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.

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:

RegionServer URL
UShttps://us-east-2.manage.dynasend.net/mcp/diagnostics
EUhttps://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.

  1. Open Settings → Cursor Settings, then click Tools & MCPs.
  2. Click Add Custom MCP.
  3. Paste the following into the mcp.json file that opens, then save:
{
"mcpServers": {
"dynasend-diagnostics": {
"url": "https://us-east-2.manage.dynasend.net/mcp/diagnostics"
}
}
}
  1. Click Connect, then sign in with Dynasend when prompted.
  2. 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.

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​

SymptomWhat to check
OAuth window never opens or is dismissedStart the connection again from the client and complete sign-in in the browser.
Connected but tools fail or return no dataConfirm you used the manage host for your tenant region.
Connection blocked on a managed networkAsk your IT administrator to allow *.manage.dynasend.net for your region.
Wrong Dynasend account authorizedSign out of Dynasend in the browser, reconnect the MCP server, and sign in with the correct account.