Nomic Atlas MCP by usefulapi

io.usefulapiPublished by usefulapi.ioOfficial publisherv1.39.2Updated Nov 14, 2026

Semantic nearest-neighbour search over your datasets, plus indices and projections.

The publisher's own server: Ably MCP by usefulapi

VerifiedStreamable HTTPWeb executableKnowledge & MemoryData & AnalyticsAI & ML

Overview

AI-generated overview

Hosted Nomic Atlas connector that lets an assistant browse Atlas datasets and run semantic nearest-neighbour searches over their embeddings.

What you can do
  • Look up the signed-in account and its organisations, and list the datasets an organisation holds
  • Fetch a dataset by id or by organisation and dataset slug, including its schema, size, indices and projections
  • Find records most similar to given record ids in embedding space, with distances
  • Check index-building job status and a projection's field schema
  • List a projection's tags and check whether a tag has finished computing
  • Report usage against the monthly call limit, request a missing feature, and manage a paid subscription
When to use it
Useful when your data already lives in Nomic Atlas and you want an assistant to explore it, inspect dataset structure, or answer questions like which records resemble a given record. It is a read-only view of Atlas, so it suits exploration and similarity lookups rather than building or editing datasets.
Requirements
Remote streamable HTTP endpoint; nothing to install locally. Connect with the server URL only, then sign in through OAuth with your Nomic Atlas credentials, which are validated and stored per user. No API key or Authorization header goes in the client config. A free plan allows 50 tool calls per month.
Before you install
You hand your Nomic Atlas credentials to the hosted service during OAuth sign-in, so trust in the operator matters. Paid plans are billed through Stripe Checkout links returned by the upgrade tool, and upgrading from Pro to Pro+ charges the price difference immediately; cancellation gives no refund for the current period. The meta tools can change your subscription, so confirm before letting an assistant run them.

Installation

In SourceWeft

  1. Open Nomic Atlas MCP by usefulapi in the dashboard and add it to a workspace.
  2. 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.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.usefulapi%2Fnomic-atlas/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "nomic-atlas-by-usefulapi": {
      "type": "http",
      "url": "https://nomic-atlas.usefulapi.io/mcp"
    }
  }
}

README

Nomic Atlas MCP by usefulapi

Semantic nearest-neighbour search over your datasets, plus indices and projections. Hosted, no local install.

Live endpoint: https://nomic-atlas.usefulapi.io/mcp · Homepage: https://usefulapi.io

Connect

  • Claude (claude.ai, Desktop): open Customize → Connectors, click + Add → Add custom connector, and paste https://nomic-atlas.usefulapi.io/mcp.
  • Claude Code: claude mcp add --transport http nomic-atlas https://nomic-atlas.usefulapi.io/mcp, then run /mcp to log in.
  • VS Code: Add to VS Code.
  • Cursor and other clients: add the URL as a remote MCP server:
json
{  "mcpServers": {    "nomic-atlas": {      "url": "https://nomic-atlas.usefulapi.io/mcp"    }  }}

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, and the login page asks for your Nomic Atlas credentials.

Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/nomic-atlas/

On first connect you'll paste your Nomic Atlas credentials. They are validated, stored per-user, and scoped to you — no keys in config files.

Tools

ToolTypeWhat it does
nomic_get_userreadGet the current user
nomic_get_organizationreadGet an organisation
nomic_get_datasetreadGet a dataset by id
nomic_get_dataset_by_slugreadGet a dataset by name
nomic_nearest_neighbors_by_idreadFind similar records
nomic_get_index_jobreadGet an index job
nomic_get_projection_schemareadGet a projection's schema
nomic_list_tagsreadList a projection's tags
nomic_get_tag_statusreadGet a tag's status
nomic_atlas_usage_statusmetaUsage status (free-tier meter)
nomic_atlas_request_featuremetaRequest a missing feature
nomic_atlas_upgrademetaUpgrade to Pro or Pro+
nomic_atlas_cancel_subscriptionmetaCancel the Pro subscription

read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.

Pricing

PlanPriceLimit
Free$050 tool calls / month
Pro$9/mo or $90/yr (2 months free)10,000 tool calls / month
Pro+$39/mo or $390/yr (2 months free)100,000 tool calls / month

Each paid plan covers this server only. Ask your AI to run nomic_atlas_upgrade and choose Pro or Pro+, billed monthly or yearly (it returns a Stripe Checkout link). If you already have Pro, ask to change it to Pro+. The change requires your confirmation, keeps your billing interval and charges the price difference for the rest of the period immediately. Cancel any time with nomic_atlas_cancel_subscription: your paid plan continues to the end of the paid period, with no refund for the current period, and asking to resume the same plan with nomic_atlas_upgrade before then undoes the cancel. Or write to [email protected].

License

MIT

Source: servers/nomic-atlas/README.md at commit f22f848

Tools

9

nomic_get_user

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.

Takes no parameters.

nomic_get_organization

Get an organisation

Fetch an organisation by slug, with the datasets it holds. Atlas: GET /v1/organization/{slug}.

Parametersslugrequired

nomic_get_dataset

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}.

Parametersdataset_idrequired

nomic_get_dataset_by_slug

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}.

Parametersdataset_slugrequiredorganization_slugrequired

nomic_nearest_neighbors_by_id

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.

Parameterskrequireddatum_idsrequiredatlas_index_idrequired

nomic_get_index_job

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}.

Parametersjob_idrequired

nomic_get_projection_schema

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.

Parametersprojection_idrequired

nomic_list_tags

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.

Parametersdataset_idrequiredprojection_idrequired

nomic_get_tag_status

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.

Parameterstag_idrequireddataset_idrequired

Version history

26
  1. v1.39.2LatestNov 14, 2026
  2. v1.39.1Nov 13, 2026
  3. v1.38.0Nov 12, 2026
  4. v1.37.3Nov 11, 2026
  5. v1.36.5Nov 8, 2026
  6. v1.36.4Nov 7, 2026
  7. v1.35.3Nov 5, 2026
  8. v1.35.2Nov 5, 2026
  9. v1.35.1Nov 4, 2026
  10. v1.35.0Nov 3, 2026
  11. v1.34.1Nov 3, 2026
  12. v1.33.0Nov 1, 2026
  13. v1.31.0Oct 31, 2026
  14. v1.30.0Oct 31, 2026
  15. v1.29.2Oct 30, 2026
  16. v1.29.0Oct 30, 2026
  17. v1.24.0Oct 26, 2026
  18. v1.21.3Oct 25, 2026
  19. v1.21.0Oct 25, 2026
  20. v1.20.0Oct 24, 2026
  21. v1.17.0Oct 23, 2026
  22. v1.16.4Oct 22, 2026
  23. v1.16.3Oct 21, 2026
  24. v1.11.1Oct 9, 2026
  25. v1.10.0Oct 9, 2026
  26. v1.0.0Sep 29, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Usefulapi integrations