Business MCP reference
Endpoint
Section titled “Endpoint”| Setting | Value |
|---|---|
| URL | https://api.inside.chat/mcp |
| Transport | Streamable HTTP, POST only, plain JSON responses, no session |
| Protocol versions | 2025-11-25, 2025-06-18, 2025-03-26 |
| Authentication | Authorization: Bearer <token> on every request, including initialize |
| Tokens | An installation token, or an OAuth token requested with resource=https://api.inside.chat/mcp |
| Resource metadata | GET /.well-known/oauth-protected-resource/mcp |
Request rules
Section titled “Request rules”Content-Type: application/jsonandAccept: application/json, text/event-stream.- After
initialize, send the negotiatedMCP-Protocol-Versionheader. - One JSON-RPC message per request. Batches are rejected.
- Request bodies are limited to 64 KiB. Query strings are rejected.
- Requests with an
Originother than the Gateway’s are rejected. GETandDELETEreturn405. NoMcp-Session-Idis issued.
Methods
Section titled “Methods”| Method | Notes |
|---|---|
initialize |
Returns server capabilities for tools, resources and prompts |
notifications/initialized, notifications/cancelled |
Accepted with 202 |
ping |
Returns {} |
tools/list |
Tools the credential can use now. No pagination. |
tools/call |
Runs one tool |
resources/list, resources/templates/list, resources/read |
Guides and data resources |
prompts/list, prompts/get |
Prompts that prepare requests |
Tool results
Section titled “Tool results”A successful call returns the REST response body in structuredContent.data, and the same JSON as text:
{ "content": [{ "type": "text", "text": "{\"data\":{...}}" }], "structuredContent": { "data": { "websites": [{ "website_id": "web_4927_123" }] } }, "isError": false}A failed call returns isError: true:
{ "structuredContent": { "error": { "code": "not_found", "status": 404, "request_id": "..." } }, "isError": true}retry_after is present, in seconds, when a quota was reached. Write tools also return operation_id next to data or error; pass it to operation_get to check the receipt.
Clients that negotiate 2025-06-18 or later receive an outputSchema for the main read tools.
Tool names
Section titled “Tool names”Each REST operation’s tool has the operation’s name, inputs and permissions. The discovery tools are gateway_context, guide_read, websites_list and capabilities_list. Realtime socket operations have no tool. See all operations.
JSON-RPC errors
Section titled “JSON-RPC errors”| Code | Meaning |
|---|---|
-32700 |
The body isn’t valid UTF-8 JSON, or is larger than 64 KiB |
-32600 |
The message isn’t a valid JSON-RPC request, or is a batch |
-32601 |
Unknown method |
-32602 |
Invalid parameters, cursor or tool request, or a tool the credential can’t use |
Authentication, origin, method and Accept failures (401, 403, 405 and 406) are returned as HTTP errors before JSON-RPC processing. See troubleshooting.