JustOneAPI MCP Server
OfficialSearch and retrieve posts from Bilibili, including keyword search, date filtering, and pagination.
Search and retrieve posts from Kuaishou, including keyword search, date filtering, and pagination.
Search and retrieve posts from WeChat, including keyword search, date filtering, and pagination.
Search and retrieve posts from Xiaohongshu, including keyword search, date filtering, and pagination.
Search and retrieve posts from Zhihu, including keyword search, date filtering, and pagination.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@JustOneAPI MCP Server Search for deepseek across all Chinese social media platforms"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
JustOneAPI MCP Server
简体中文 | English
Use JustOneAPI in MCP clients such as ChatGPT, Codex, Cursor, Hermes Agent, and other AI assistant tools.
JustOneAPI MCP helps your assistant find the right JustOneAPI endpoint, inspect the required parameters, and call APIs through your JustOneAPI authorization.
Supported Clients
JustOneAPI MCP supports remote Streamable HTTP and local stdio. Current verified and compatibility paths include:
ChatGPT web Developer mode MCP connections: OAuth, verified.
Codex CLI and the Codex IDE extension: OAuth, verified.
Cursor, Hermes Agent, and other clients with custom headers: existing API Token compatibility method.
Claude.ai, Claude Desktop, and Claude Code: OAuth remains under compatibility testing; Claude Code can use an existing API Token header.
Clients with a compatible OAuth registration flow can connect with only the remote URL and complete authorization in the browser. Compatibility also depends on client registration support and account or workspace policy. Clients without OAuth can keep using a legacy API Token header or local stdio.
Related MCP server: MCP from API
Quick Start
Remote HTTP with OAuth
OAuth is enabled on the production service. Add this URL as an MCP connection:
https://mcp.justoneapi.com/mcpCompatible clients discover the protected-resource metadata, redirect you to
auth.justoneapi.com, and ask for the MCP scopes shown on the consent page.
No JustOneAPI API Token needs to be pasted into the client. Entry points, OAuth
registration methods, and account restrictions vary by client, so the setup
below lists only verified OAuth paths.
Client setup
ChatGPT web: open
Settings → Security and login, enableDeveloper mode, openPlugins, and select+. Enter a name, description, and the/mcpURL above, then choose OAuth for Authentication. After creating the connection, ChatGPT discovers the authentication metadata and starts authorization during connection or when a protected tool is first invoked. Developer mode availability can depend on the ChatGPT account and workspace policy.Codex CLI / IDE extension: run the commands below. The currently recommended setup explicitly uses the verified DCR registration path:
codex mcp add justoneapi \
--url https://mcp.justoneapi.com/mcp
codex mcp login justoneapi \
--oauth-client-registration dcrThe ChatGPT desktop app, Codex CLI, and Codex IDE extension share MCP configuration on the same Codex host. See the official OpenAI MCP documentation and ChatGPT connection testing guide for current entry points.
OAuth for Claude.ai, Claude Desktop, and Claude Code remains under compatibility
testing and is not yet offered as a generally supported OAuth connection.
Claude Code can use an existing API Token with
--header "Authorization: Bearer your_token"; do not treat the generic JSON
below as a Claude Code configuration.
The authorization page shows the requested scopes. An account owner selects an existing API Token or creates a dedicated one; a Token Member can only use the Token assigned to that member. Disconnecting the app later revokes only its OAuth connection; it does not disable or delete the linked API Token.
Remote HTTP with an existing API Token
The existing header-based connection remains supported for compatibility:
{
"mcpServers": {
"justoneapi": {
"url": "https://mcp.justoneapi.com/mcp",
"headers": {
"Authorization": "Bearer your_token"
}
}
}
}Local stdio
As of 2026-08-25, npm latest is still the legacy 1.0.1 package, not the v2
implementation in this repository. If you require local stdio, pin the version
so the legacy CLI is not mistaken for the hosted v2 service:
{
"mcpServers": {
"justoneapi": {
"command": "npx",
"args": ["-y", "justoneapi-mcp@1.0.1"],
"env": {
"JUSTONEAPI_TOKEN": "your_token"
}
}
}
}Legacy 1.0.1 supports Node.js 18 or newer, and its tool layout is not the same as
the hosted v2 service. OAuth applies only to the remote Worker; stdio continues
to read JUSTONEAPI_TOKEN locally. Update this version guidance after v2 is
actually published to an npm dist-tag.
Catalog builds and dynamic releases use built-in public-safety validation and require no operator security registry or secret. Runtime API and account calls return the upstream payload without MCP-layer response truncation.
Authentication and scopes
OAuth users select the API Token to link on the authorization page and do not paste it into the client. The existing API Token remote compatibility method uses:
Authorization: Bearer your_tokenor, for local stdio:
JUSTONEAPI_TOKEN=your_tokenLocal stdio uses the environment variable above. Never commit a real Token to a repository.
OAuth access tokens use three least-privilege scopes:
mcp:catalog:read— search endpoints, inspect schemas, and list platforms.mcp:api:call— call a JustOneAPI endpoint.mcp:account:read— view balance and usage.
call_endpoint may incur charges under the API Token linked during OAuth and
its current pricing, permissions, balance, and budget. It validates the
endpoint and parameters before obtaining a short-lived delegation token, then
makes exactly one upstream dispatch. It does not automatically retry an
uncertain timeout, network failure, or HTTP 502/503/504 result.
Legacy API Tokens are still sent to the JustOneAPI backend in the established query/form format. OAuth access and delegation tokens are never put in backend URLs or form bodies; delegation tokens are sent only as an Authorization Bearer header.
Operator rollout
Production currently runs in dual mode. OAuth is additive and feature-flagged,
and these switches remain the deployment and rollback boundary:
JUSTONEAPI_OAUTH_MODE=offkeeps the remote service legacy-only and hides OAuth discovery metadata.JUSTONEAPI_OAUTH_MODE=dualaccepts both existing API Tokens and standard OAuth on the exacthttps://mcp.justoneapi.comorigin.Preview and
workers.devroutes remain legacy-only, even if the variable is set todual.
The Worker uses private_key_jwt for Authorization Server introspection and
RFC 8693 token exchange. Store the private JWK set and active kid as Worker
secrets; never commit .dev.vars, PEM files, or private JWK sets. Rotate keys by
publishing old and new public keys first, switching the active kid second, and
removing the retired key only after the overlap period.
npm 2.0 will first be published under the next dist-tag through OIDC trusted
publishing. After the exact published artifact passes the Node.js 20, 22, and
24 smoke checks, an operator promotes it separately with npm 2FA using
npm dist-tag add justoneapi-mcp@2.0.0 latest. This is never automated with an
NPM_TOKEN. See RELEASE.md.
Things You Can Ask
Ask your MCP client naturally:
Find the Xiaohongshu note comments API and tell me which parameters are required.More examples:
Which Douyin APIs can get video details?Call the Xiaohongshu note comments API with this note ID: xxxxx.List the Weibo search-related APIs and explain when to use each one.Continue to the next page of results.Check my JustOneAPI balance.Show my recent API usage and spending.The API returned code 400. Help me check which parameter might be wrong.The API returned code 601 or 602. What does it mean?The assistant can search available JustOneAPI endpoints, explain required parameters, call the selected API after you provide the needed values, and help interpret common response codes.
License
MIT
Available Tools
7 toolscall_endpointCall endpoint (may incur charges)ADestructive
Validate params and make one JustOneAPI endpoint call by endpoint_id. The call may incur charges under the bound API Token's current pricing and budget. Params should use snake_case names from get_endpoint_schema.
Inputs: endpoint_id (required), params. Returns: object
get_account_balanceGet account balanceARead-onlyIdempotent
Get the current JustOneAPI token's available balance and currency. Use this when the user asks about account balance, remaining balance, or whether the token can continue calling APIs.
Inputs: no named parameters. Returns: object
get_endpoint_schemaGet endpoint schemaARead-onlyIdempotent
Get the full schema and parameter contract for an endpoint_id returned by search_endpoints.
Inputs: endpoint_id (required). Returns: object
get_usage_summaryGet usage summaryARead-onlyIdempotent
Get the current JustOneAPI token's API usage and spending summary, including recent call trends and spending trends.
Inputs: no named parameters. Returns: object
list_platformsList platformsARead-onlyIdempotent
List supported JustOneAPI platforms and endpoint counts.
Inputs: no named parameters. Returns: object
refresh_catalogRefresh catalogADestructive
Admin-only. Refresh the endpoint catalog from JustOneAPI OpenAPI documents.
Inputs: force, rollback. Returns: object
search_endpointsSearch endpointsARead-onlyIdempotent
Find JustOneAPI endpoint candidates from natural language. Returns endpoint_id candidates; call get_endpoint_schema next.
Inputs: query (required), limit, platform, include_hidden, +1 more. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 7 tools
Each tool has a clearly distinct role: discovery, schema retrieval, invocation, account balance, usage analytics, platform listing, and catalog refresh. The two account-related tools are separated by balance vs. spending trends, and the sequential workflow tools explicitly reference each other.
All tool names follow a consistent verb_noun snake_case pattern: search_, get_, call_, list_, refresh_. There are no mixed naming conventions or vague verbs, making the set predictable and easy to navigate.
Seven tools is well-scoped for an API aggregation/catalog service. Each tool supports a necessary part of the workflow or administrative/maintenance need without redundant or filler tools.
The core workflow is fully covered: search for endpoints, retrieve their schema, call them, and check account balance/usage afterward. Platform listing and catalog refresh round out the surface with no obvious dead ends or missing lifecycle steps.
Maintenance
Related MCP Connectors
All public upAPI operations as MCP tools: web scraping, search, screenshots, PDF, OCR and more.
One MCP endpoint over every Valksor dictionary: namespaced tools plus a JSON passthrough.
All 36 Edge Thirteen MCP tools (SEC filings, WCAG, entity diligence, more) in one endpoint.
Related MCP Servers
- AlicenseCqualityDmaintenanceEnables interaction with the OpenData Platform API by dynamically exposing all endpoints as MCP tools with typed input schemas and HTTP handlers.99MIT
- FlicenseNot gradedqualityDmaintenanceEnables users to expose arbitrary HTTP APIs as configurable MCP tools by defining tool specifications in a JSON configuration file.3-
- AlicenseNot gradedqualityDmaintenanceProvides a standardized MCP interface for interacting with Shopify tools and services, enabling unified API access and compatibility with MCP-compliant clients.1MIT
- AlicenseNot gradedqualityDmaintenanceExposes the UniFi Network Integration API as MCP tools, dynamically loaded from JSON manifests, with read-only mode by default.MIT