
Communicate Developer Docs
io.github.uditgoenkav1.0.0Updated Oct 1, 2026
Read-only access to Communicate developer guides, OpenAPI summaries, and support contact.
Overview
AI-generated overview
Gives an assistant read-only access to Communicate developer guides, OpenAPI summaries, and support contact details.
- What it does
- This remote MCP server exposes Communicate's developer documentation to an assistant. According to the registry description, it provides read-only access to developer guides, OpenAPI summaries, and support contact information. No individual tools are listed in the manifest, so the exact tool names and parameters are not documented here.
- When to use it
- Useful when an assistant needs to look up Communicate developer documentation or API summaries while helping with integration work, or when it needs the support contact route. It is a documentation lookup server, not a tool for changing anything in an account.
- Requirements
- A remote streamable HTTP endpoint at communicate.so; no packages, environment variables, or headers are declared. The manifest declares no authentication, and the server is marked as web executable.
Before you install
The manifest declares no authentication and no credentials, so nothing secret is requested. Because it is read-only documentation access, no data is written, sent, or deleted through it. Confirm the endpoint and any terms directly with the provider before relying on it.
Installation
In SourceWeft
- Open Communicate Developer Docs in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"communicate-docs": {
"type": "http",
"url": "https://communicate.so/mcp"
}
}
}Tools
0Tool metadata has not been indexed yet.
Version history
1- v1.0.0LatestOct 1, 2026

