Remato exposes a Model Context Protocol server that lets AI assistants call the Remato external API as tools — list projects, manage tasks, query crew, pull time reports, and more.
| URL | https://api.ai-tools.remato.com/mcp |
| Transport | Streamable HTTP |
| Auth | x-api-key: <Remato API key> |
| Health probe | GET <https://api.ai-tools.remato.com/mcp/health> (no auth) |
| Rate limit | 100 req/min per key |
Contact Remato Support at [email protected] for API access.
Every config below points at the same URL with the same x-api-key header. Replace <your-api-key> with your Remato API key.
claude mcp add --transport http remato <https://api.ai-tools.remato.com/mcp> \
--header "x-api-key: <your-api-key>"
Verify with claude mcp list.
Create ~/.cursor/mcp.json (global) or .cursor/mcp.json in the project root:
{
"mcpServers": {
"remato": {
"url": "<https://api.ai-tools.remato.com/mcp>",
"headers": {
"x-api-key": "<your-api-key>"
}
}
}
}
Cursor probes Streamable HTTP first and falls back to SSE automatically.
Edit .vscode/mcp.json (workspace) or your user-profile mcp.json (Command Palette → MCP: Open User Configuration):
{
"servers": {
"remato": {
"type": "http",
"url": "<https://api.ai-tools.remato.com/mcp>",
"headers": {
"x-api-key": "${input:remato-api-key}"
}
}
},
"inputs": [
{
"type": "promptString",
"id": "remato-api-key",
"description": "Remato API key",
"password": true
}
]
}
Note: VS Code uses servers (not mcpServers). The first time the server starts, VS Code prompts for the key and stores it in the secret store.
{
"context_servers": {
"remato": {
"url": "<https://api.ai-tools.remato.com/mcp>",
"headers": {
"x-api-key": "<your-api-key>"
}
}
}
}