MCP server

NoSite for your agents

Two endpoints, two jobs. /mcp/docs teaches your agent the API and needs no login. /mcp/data acts on your account after you sign in and approve - and asks before it spends a credit.

For developers integrating the REST API. Once added, Claude Code, Codex, Cursor or Claude Desktop knows the API exactly - every endpoint, field and error - and writes correct integration code the first time instead of guessing from a docs page. No key needed.

Install

Claude Code
claude mcp add --transport http nosite https://nosite.app/mcp/docs
Codex CLI (~/.codex/config.toml)
[mcp_servers.nosite]
url = "https://nosite.app/mcp/docs"
Cursor / Claude Desktop / any MCP client (JSON config)
{
  "mcpServers": {
    "nosite": { "url": "https://nosite.app/mcp/docs" }
  }
}

Then ask your agent: “Using the NoSite API, write a script that pulls untouched bakeries in Cairo with a phone number and reveals the first five.” It will use real parameter names, the {data, meta} envelope and the right error codes.

Tools

nosite_api_overviewAuth, envelope, error codes, rate limits, credits, pagination and the endpoint list - the whole API in one call.
nosite_api_endpointOne endpoint in full: every parameter, request body, response field, error code, an example response and a curl.
nosite_api_schemaField-by-field definition of Lead, Contact, ContactUpdate and the other objects.
nosite_api_searchWhere does “whatsapp” or “daily cap” or “since” live? Matching endpoints, params, fields and errors.

Always in sync - the tools read the same live schema as /api/docs.