Semantic nearest-neighbour search over your datasets, plus indices and projections. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"nomic-atlas": {
"url": "https://nomic-atlas.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"nomic-atlas": {
"type": "http",
"url": "https://nomic-atlas.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Nomic Atlas API key.
Create one at atlas.nomic.ai → your profile → API keys. Your token is used only to call the API on your behalf and to derive a private account id; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Nomic Atlas API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Nomic Atlas connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
nomic_get_user | read | Get the current user Fetch the account the API key belongs to, including the organisations it can access. Start here — the organisation slug feeds the other tools. Atlas: GET /v1/user. |
nomic_get_organization | read | Get an organisation Fetch an organisation by slug, with the datasets it holds. Atlas: GET /v1/organization/{slug}. |
nomic_get_dataset | read | Get a dataset by id Fetch a dataset (Atlas calls it a project) by id — its schema, size, indices and projections. Atlas: GET /v1/project/{id}. |
nomic_get_dataset_by_slug | read | Get a dataset by name Fetch a dataset by organisation slug and dataset slug — the human-readable path, and usually easier than finding the UUID. Atlas: GET /v1/project/{organization_slug}/{project_slug}. |
nomic_nearest_neighbors_by_id | read | Find similar records Semantic search: given the ids of records already in a dataset, return their nearest neighbours in embedding space, with distances. This is what Atlas is for — finding what resembles what across unstructured data. Needs a BUILT index; if the map is still building the call fails with a 500, so check nomic_get_index_job. Atlas: POST /v1/project/data/get/nearest_neighbors/by_id. |
nomic_get_index_job | read | Get an index job Fetch the status of an index-building job. Atlas indexes take time to build, and a vector search against an unbuilt map fails — this is how you tell which it is. Atlas: GET /v1/project/index/job/{job_id}. |
nomic_get_projection_schema | read | Get a projection's schema Fetch the field schema of one projection — the columns available on its records. Atlas: GET /v1/project/projection/{projection_id}/schema. |
nomic_list_tags | read | List a projection's tags List the tags defined on one projection — the labelled selections a person made on the map. Atlas: GET /v1/project/projection/tags/get/all. |
nomic_get_tag_status | read | Get a tag's status Check whether a tag has finished computing its membership. A tag that is still building returns partial results. Atlas: GET /v1/project/projection/tags/status. |
nomic_atlas_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
nomic_atlas_request_feature | Request a missing feature Tell usefulapi that the user needs something the Nomic Atlas tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
nomic_atlas_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Nomic Atlas tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
nomic_atlas_cancel_subscription | Cancel the Pro subscription Cancel the caller's Nomic Atlas Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run nomic_atlas_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Pro | $9/mo · $90/yr | Unlimited |
Pro covers this Nomic Atlas server only. Subscribe with nomic_atlas_upgrade (it returns a Stripe Checkout link). Cancel any time with nomic_atlas_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running nomic_atlas_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Nomic Atlas. The server calls the Nomic Atlas API with your own Nomic Atlas access, so it sees only the data that your account can see.
The login page asks for your Nomic Atlas API key. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Nomic Atlas API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Nomic Atlas API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Nomic Atlas.
All 9 Nomic Atlas tools are marked read-only.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Nomic Atlas server only. Run nomic_atlas_usage_status to see how many calls you used.
Ask the AI to run nomic_atlas_upgrade: it returns a Stripe Checkout link. To cancel, run nomic_atlas_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with nomic_atlas_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.