Remote MCP#
Deployment pending. No production endpoint is advertised yet. The following
client configurations describe documented native support; they are not claims
of successful model tool selection or directory approval. Set REMOTE_MCP_URL
to the production HTTPS /mcp URL after the deployment receipt confirms it.
The optional remote service provides zero-install, read-only access to the
same canonical Python resolver as PyPI 0.3.0. Remote V1 is Wikidata-only.
Google KG is disabled, including fallback and crosschecks; requesting it returns
UNSUPPORTED_REMOTE_PROVIDER. Local PyPI/stdio retains optional
Google KG with your own key. No user sign-in, provider key or OAuth is required.
Transport and availability#
Send one JSON-RPC message to POST /mcp using Streamable HTTP. Responses are JSON;
there is no legacy SSE transport or session persistence. GET/DELETE return 405.
The SDK supports legacy initialize and the current stateless protocol. See
the current MCP transport specification.
All gateway HTTP admissions share 100,000 requests per UTC day. Setup, tools/list, notifications, invalid messages, unknown paths and burst rejections count before resolver execution. A SQLite Durable Object atomically increments the authoritative count. It resets on the first admitted request after UTC midnight. Concurrency and restarts do not create separate counters.
Exhaustion returns HTTP 429, JSON-RPC error
PUBLIC_DAILY_QUOTA_EXHAUSTED, error.data.reset_at, Retry-After and
X-Quota-Reset. The service intentionally remains unavailable until midnight
UTC. Accounting failure returns 503 and never executes the resolver. There is
no overflow into unlimited resolver usage. Cloudflare bills rejected ingress
on Workers Paid; this admission ceiling is not a total platform billing cap.
Burst controls add a 600/minute global ceiling and an approximate 300/minute network gate. Shared networks may encounter burst rejection. Availability is best effort. Read privacy and service limitations.
Tool limits#
| Tool | Public bound |
|---|---|
| kg_search | default 3, maximum 5 candidates |
| kg_discover_identity | one envelope, default 3, maximum 5 candidates |
| kg_lookup_entities | maximum 10 QIDs |
| kg_related | depth 2, maximum 10 results |
| kg_entity | up to 12 selected properties, 3 evidence properties |
| kg_audit_identity | one bounded existing-identity envelope |
| kg_resolve | one bounded identity resolution |
| kg_status | Wikidata configuration, Google disabled, limits |
Each HTTP request permits at most eight upstream attempts across all phases, zero retries, 5 seconds per upstream request and 20 seconds per tool request. Input: 16 KiB, depth 12, strings/URLs 512 characters, aliases 8. Tool text: 6000 UTF-8 bytes; full response: 64 KiB. Runtime CPU/subrequest ceilings remain provisional until measured deployment acceptance. Raw SPARQL, unrestricted graphs and corpus batches remain local CLI workflows.
Provider concordance is not local identity proof. sameAs candidates are for review, not automatically approved public links. Preserve HOLD and AMBIGUOUS.
OpenAI, ChatGPT and Codex#
For OpenAI Responses API remote MCP, use a native tool configuration:
{"type":"mcp","server_label":"wikidata_knowledge","server_url":"REMOTE_MCP_URL","require_approval":"always"}
A portable plugin ZIP uses mcp.json:
{"mcpServers":{"wikidata_knowledge":{"type":"streamable-http","url":"REMOTE_MCP_URL"}}}
ChatGPT custom connectors require access to the appropriate account feature. Public plugin distribution additionally requires review and publisher/domain verification under OpenAI's submission process. Configuration does not mean directory publication.
Claude#
Use Settings → Connectors → Add custom connector and enter the production URL, with no OAuth configuration. See Claude's custom connector instructions. Public distribution uses the separate Single MCP connector route in the directory submission portal. A custom connection does not approve the directory listing.
Gemini API and Deep Research#
Interactions remote MCP uses Streamable HTTP and a snake_case server name:
from google import genai
client = genai.Client()
tools = [{"type": "mcp_server", "name": "wikidata_knowledge",
"url": "REMOTE_MCP_URL",
"allowed_tools": ["kg_search", "kg_entity", "kg_audit_identity", "kg_discover_identity"]}]
result = client.interactions.create(
model="gemini-3.8-flash", tools=tools,
input="Find a Wikidata candidate for Universe and inspect its selected facts.")
For Deep Research,
use the same tools with agent="deep-research-preview-04-2026" and
background=True instead of model. Deep Research inference is billed under
Google's pricing.
These examples were documentation-checked, not inference-tested. Google's
Interactions overview still contains a conflicting Gemini 3 remote-MCP
limitation; model-specific availability must be verified before making claims.
Antigravity#
The current custom configuration
uses serverUrl in global or workspace mcp_config.json:
{"mcpServers":{"wikidata_knowledge":{"serverUrl":"REMOTE_MCP_URL"}}}
An official curated MCP Store exists. No open publisher submission path has been verified for this project. A working custom config is not Store approval.
Microsoft Copilot Studio#
Use the MCP onboarding wizard with the HTTPS endpoint, Streamable transport and no authentication. Generic consumer Copilot access is not established by a Copilot Studio configuration. Certification is a separate Partner Center workflow requiring publisher/account eligibility.
Cursor#
Cursor remote MCP accepts:
{"mcpServers":{"wikidata_knowledge":{"url":"REMOTE_MCP_URL"}}}
Add this to the appropriate project/global MCP configuration. Existing local stdio and Smithery Local remain available. Remote configuration does not waive any repository requirement for the Cursor Marketplace.