Compoid MCP vs Sanity
A side-by-side look at the Compoid MCP and Sanity MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Compoid MCP for developer tools work as a local process; choose Sanity for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Compoid MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
COMPOID_REPO_API_URL, COMPOID_REPO_API_KEY, COMPOID_AI_API_URL, COMPOID_AI_API_KEY, COMPOID_AI_MODEL, COMPOID_UPLOAD_URL, UPLOAD_AUTH_TOKEN, DOWNLOAD_PATH. - You want tools like
Compoid_search_records, Compoid_search_communities, Compoid_get_record_details.
Choose Sanity when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
- You want tools like
query_documents, create_documents, patch_documents.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 57/100 · Good | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Not declared |
| Required env vars | COMPOID_REPO_API_URLCOMPOID_REPO_API_KEYCOMPOID_AI_API_URLCOMPOID_AI_API_KEYCOMPOID_AI_MODELCOMPOID_UPLOAD_URLUPLOAD_AUTH_TOKENDOWNLOAD_PATH | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 192 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 13 | 8 |
| Full listing | View Compoid MCP | View Sanity |
Tools & capabilities
Compoid MCP tools 13
Compoid_search_recordsSearch for records (images, videos, papers, articles, analysis) in Compoid.Compoid_search_communitiesSearch for communities in Compoid.Compoid_get_record_detailsGet detailed information about a specific record by its Compoid ID or OAI.Compoid_get_community_detailsGet detailed information about a specific community by its Compoid ID or OAI.Compoid_download_filesDownload record files in a zip archive if available through open access.Compoid_upload_fileUpload a file to the Compoid MCP server. Accepts a data URI (data:<mime>;base64,<data>). Returns the server-side path to use as file_upload in Compoid_create_record or Compoid_update_record.Compoid_create_recordCreate a new Compoid record and submit it to a community for review. Required: community_id: community slug (e.g. 'physics' - browse https://www.compoid.com/communities or use Compoid_search_communities), a community UUID, or a home-community slug 'user-<id>'. file_upload: the file to attach. Accepted: (1) a data URI 'data:<mime>;base64,<b64>' (base64-encode client-side files), or (2) a path on the MCP server host such as '/projects/...' (e.g. the path returned by Compoid_upload_file). Plain client-local paths are NOT accessible to the server. creators: non-empty list of author / AI-model names (e.g. ['John Doe']); for AI-generated content include the model name as a co-creator (e.g. ['Qwen']). keywords: non-empty list of tags (e.g. ['Compoid', 'MCP']) - records without keywords are hard to discover. Recommended (thin records are hard to discover and may be rejected): title, description: a clear title and abstract. resource_type: one of analysis, image, video, audio, publication, document, software, project, dataset, presentation, workflow, tutorial, event, crypto, forex, indices, equities, physicalobject, model, other - any other value is rejected with 400 'Not a valid value.' (when omitted it is inferred from the file MIME type). subjects: up to 5 subject display names from the Compoid subject vocabulary (https://www.compoid.com/subjects); invalid names cause a 400. "Artificial Intelligence" is always appended as a default subject.Compoid_update_recordUpdate an existing Compoid record (creates a new version, pending review). Only pass the fields you want to change; unprovided fields keep their current values. An update with no changed fields is rejected as a no-op. Required: work_id: the record to update - a published record PID (e.g. '4171t-rc787'), a full record URL, or its OAI. Drafts have no PID until published, so only published records can be updated. Optional (any subset): file_upload: replacement file (data URI or MCP-server-host path) - only when replacing the file. title, description, creators, keywords, references: metadata to change. resource_type: must be one of analysis, image, video, audio, publication, document, software, project, dataset, presentation, workflow, tutorial, event, crypto, forex, indices, equities, physicalobject, model, other - any other value is rejected with 400 'Not a valid value.' subjects: up to 5 subject display names (https://www.compoid.com/subjects). Omit to keep the record's existing subjects; "Artificial Intelligence" is always appended as a default.Compoid_delete_recordDelete a published Compoid record. IRREVERSIBLE. The record is tombstoned and drops out of all search results. Use it to clean up test records. Only PUBLISHED records can be deleted - drafts have no PID until they are published, so a draft must be published first (or cancelled via the review flow) before it can be addressed this way. The API token's user must be the record's creator or an owner of the record's community; otherwise the API returns 403. Required: work_id: the record to delete - a published record PID (e.g. '4171t-rc787'), a full record URL (https://www.compoid.com/records/<pid>), or its OAI. On success returns a confirmation (HTTP 204). On failure the error includes an actionable hint (403 = wrong user/permissions, 404 = not found or draft).Compoid_create_communityCreate a new community on Compoid.Compoid_update_communityUpdate an existing community on Compoid. Only supply the fields you want to change.Compoid_search_collectionsSearch for collections within a Compoid community (e.g. Publications, Datasets, subject collections). community_id accepts a UUID or slug; omit query to list all collections.- +1 more on the listing page
Sanity tools 8
query_documentsrun GROQ queries directlycreate_documentscreate draft documents from structured content, or version documents when a release ID is providedpatch_documentssurgical edits to existing documents; published documents are edited by creating or updating draftsdeploy_studiodeploy a hosted Studio bound to an MCP-managed schemacreate_versioncreate version documents for releaseswhoamiverify the authenticated Sanity userget_project_studioslist Studio applications linked to a projectgive_feedbackreport MCP tool errors, missing capabilities, confusing output, or documentation issues
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Compoid MCP
{
"mcpServers": {
"compoid-mcp-3": {
"command": "uvx",
"args": [
"compoid-mcp"
],
"env": {
"COMPOID_REPO_API_URL": "YOUR_COMPOID_REPO_API_URL_HERE",
"COMPOID_REPO_API_KEY": "YOUR_COMPOID_REPO_API_KEY_HERE",
"COMPOID_AI_API_URL": "YOUR_COMPOID_AI_API_URL_HERE",
"COMPOID_AI_API_KEY": "YOUR_COMPOID_AI_API_KEY_HERE",
"COMPOID_AI_MODEL": "YOUR_COMPOID_AI_MODEL_HERE",
"COMPOID_UPLOAD_URL": "YOUR_COMPOID_UPLOAD_URL_HERE",
"UPLOAD_AUTH_TOKEN": "YOUR_UPLOAD_AUTH_TOKEN_HERE",
"DOWNLOAD_PATH": "YOUR_DOWNLOAD_PATH_HERE"
}
}
}
}
Sanity
{
"mcpServers": {
"sanity": {
"command": "npx",
"args": [
"-y",
"sanity@latest"
]
}
}
}
Frequently asked questions
Compoid MCP is categorized under Developer Tools and uses a local stdio subprocess. Sanity belongs to Developer Tools and uses a local stdio subprocess. Pick Compoid MCP for developer tools work and Sanity for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Compoid MCP has no declared pricing — check the project's own site. Sanity has no declared pricing — check the project's own site. Auth: oauth 2.0. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add compoid-mcp-3 and sanity as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Compoid MCP has a quality signal of 57/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Sanity has 64/100 (Good) with 1 views, 0 installs and 192 GitHub stars.