Other · Remote MCP server
Apiosk Connect
Discover, pay for, execute, and publish APIs through Apiosk.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.obcraft/apiosk-mcp- Version
- 1.7.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm, PyPI
- Published
- 2026-07-22
- Updated
- 2026-07-22
- Publisher
- obcraft (GitHub)
- Website
- apiosk.com
- Repository
- github.com/obcraft/apiosk-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.apiosk.com/mcp | None |
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @apiosk/mcp | 1.7.0 | stdio |
| PyPI | apiosk-mcp | 1.7.0 | stdio |
How to connect Apiosk Connect
Apiosk Connect is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.apiosk.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: @apiosk/mcp version 1.7.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y @apiosk/mcp@1.7.0. It reads these environment variables: APIOSK_PRIVATE_KEY (secret) and APIOSK_CONNECT_TOKEN (secret); set them in the client's configuration for this server.
It can also run locally from a Python package published to PyPI: apiosk-mcp version 1.7.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install — the usual command is uvx apiosk-mcp. It reads these environment variables: APIOSK_PRIVATE_KEY (secret) and APIOSK_CONNECT_TOKEN (secret); set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"apiosk-mcp": {
"command": "npx",
"args": [
"-y",
"@apiosk/mcp@1.7.0"
],
"env": {
"APIOSK_PRIVATE_KEY": "<secret>",
"APIOSK_CONNECT_TOKEN": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| Api GovernanceSigned, offline-verifiable contract-change authorization. Only a granted change can proceed. | Remote · HTTP |
| API.market MCP GatewayConnect AI agents to 580+ APIs with OAuth or API-key auth. Hosted gateway; API pricing varies. | Remote · HTTP |
| apidx UUID GeneratorRandom UUID v4 (RFC 9562) as an HTTP API: 1-100 UUIDs per call, in uuid, URN, hex or integer... | Remote · HTTP |
| APIFreaks MCPAPIFreaks MCP: live APIs for agents. Enable modules with ENABLE_MODULES; discover via list_modules. | Local · stdio |
| ApipayPrepaid balance for AI agents: one key, 4,900+ tools your agent can run today, caps, receipts. | Remote & Local · HTTP, stdio |
| Apis GuruAPIs.guru MCP — keyless directory of 2,500+ public APIs and their OpenAPI specs. | Remote · HTTP |
| Apis Guru MCPBrowse the APIs.guru directory of public APIs with metadata and versions. No key required. | Local · stdio |
| Apis IoDiscover, rate and compare APIs and providers in the APIs.io catalog; manage a listing you own. | Remote · HTTP |