Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
Apiosk Connect
Overview
Description from the maker (original English)
Discover, pay for, execute, and publish APIs through Apiosk.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Computer or cloud
- Transport: stdio, Streamable HTTP
- Category: Other
- You need to fill in: APIOSK_PRIVATE_KEY, APIOSK_CONNECT_TOKEN
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on the maker’s server: what you ask it goes through their server.
- You fill in yourself:
APIOSK_PRIVATE_KEY,APIOSK_CONNECT_TOKEN
Values marked secret are keys to your account. Never share them or paste them into a chat.
You need
- Runs in the cloudNothing to install; it connects over the internet
- npmNode.js installed (for the npx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
- Open Settings → Connectors
- Press Add custom connector
- Paste the address below and press Add
- If it asks you to sign in, sign in with the maker
https://mcp.apiosk.com/mcpOr run it on your computer
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"apiosk": {
"command": "npx",
"args": [
"-y",
"@apiosk/mcp"
],
"env": {
"APIOSK_PRIVATE_KEY": "your-value",
"APIOSK_CONNECT_TOKEN": "your-value"
}
}
}
}Run this in your terminal
claude mcp add --transport http apiosk https://mcp.apiosk.com/mcpOr run it on your computer
claude mcp add apiosk --env APIOSK_PRIVATE_KEY=your-value --env APIOSK_CONNECT_TOKEN=your-value -- npx -y @apiosk/mcpFill in the empty values before running it.
Or copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"apiosk": {
"url": "https://mcp.apiosk.com/mcp"
}
}
}Or run it on your computer
Or copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"apiosk": {
"command": "npx",
"args": [
"-y",
"@apiosk/mcp"
],
"env": {
"APIOSK_PRIVATE_KEY": "your-value",
"APIOSK_CONNECT_TOKEN": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"apiosk": {
"type": "http",
"url": "https://mcp.apiosk.com/mcp"
}
}
}Or run it on your computer
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"apiosk": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@apiosk/mcp"
],
"env": {
"APIOSK_PRIVATE_KEY": "your-value",
"APIOSK_CONNECT_TOKEN": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
- Open ChatGPT on the web → Settings → Connectors (Apps)
- Press Create or Add (some plans need Developer mode under Advanced first)
- Paste the address below, give it a name and save
- If it asks you to sign in, sign in with the maker
https://mcp.apiosk.com/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
Values you fill in
- Optional wallet private key for automatic x402 payments.
- Optional dashboard-managed access token.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
We have not read this server’s tool list yet; we check endpoints in rotation.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account obcraft, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- … Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
- … Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
- … Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint
Compared with others in Otheri
- More stars than 0% of the other 18334 servers in this category
- Published to the registry more recently than 16% of the other 18334 servers in this category
- Basic checks equal to or better than 100% of the other 18334 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Apiosk Connect safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
You need to fill in: APIOSK_PRIVATE_KEY, APIOSK_CONNECT_TOKEN
Does it run on my computer or in the cloud?
Either way works: install it on your computer or connect to the cloud version.
Is it still maintained?
The GitHub repo last changed –, and the latest version (1.7.0) reached the registry 4 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, ProAgentStore
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated 2 days ago
Install
ProAgentStore
by ProAgentStore
MCP-first control plane for ProAgentStore agents and private instances.
Runs in the cloudUpdated today
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Apiosk MCP
@apiosk/mcp 3.0.0 brings the Apiosk Ask workflow to Claude, Codex and other MCP hosts: ask a question, compare matching sources, review inputs and one total, approve that request, and inspect saved results. It uses the existing Gateway for discovery, planning, prices, execution and evidence.
MCP1 card URLs, connection identity, token formats and cached Ask tool signatures remain compatible. Compatibility operations stay private to cards; new model connections continue to see Ask first. Both old and new approval calls share the same durable approval record.
The default is question-scoped source discovery. There is no global “browse the catalog” flow. For example, “What does ASML do?” should first call apiosk_ask with that question and display its matching sources; a model's general knowledge is not an Apiosk result.
This repository is the canonical obcraft/apiosk-mcp implementation. Versioned source and manifests do not establish that this version has been deployed, published or installed in a host.
Ask interactions and embedded components
The server exposes 36 public tools and six private component operations, saved-request resources and an Ask prompt. The actual App Ask React components and design tokens are vendored in src/ask-page/ and compiled into the self-contained embedded resource. The local tester loads that same resource. src/ask-ui/ retains the original MCP transport and compatibility renderers; every operation still uses the durable saved-request and approval journal.
Source discovery uses the App’s filtering, deduplication and provider ordering. Offered endpoint descriptors enrich matching sources without adding unrelated catalog entries. Account display currency comes from Gateway’s read-only /v2/display-context; quoted atomic amounts remain unchanged. Rebuild the embedded bundle with npm run build:ask-page after editing its sources.
Manual source selection prepares each chosen native endpoint with the App’s exact input values. Connected clients use /v2/ask/source/prepare, which requires explicit approval even when the connection has a standing spending rule. The MCP combines those saved quotes into one reviewed maximum; preparation does not purchase data.
MCP Apps and ChatGPT-compatible metadata identify the embedded resources. Model-visible results carry compact source identifiers, status, input needs and the exact approval. Full component data travels separately in _meta.apiosk_card_data, so large source schemas and raw response trees do not flood the model context. Saved evidence remains available through the result and evidence tools.
Hosts that support embedded components can show the interactive cards. Text-only hosts receive structured results and use the public tools. Support and rendering still depend on the host; passing local tests does not establish installed Claude, Codex or ChatGPT acceptance. Read-only HTML exports are separate from interactive cards.
| Interaction | Tools |
|---|---|
| Ask and inspect matching sources | apiosk_ask, apiosk_sources |
| Edit source inputs and prepare one total | apiosk_prepare |
| Review and explicitly approve the exact quote | apiosk_approve |
| Read progress, refresh prices, supply choices or missing input | apiosk_status, apiosk_requote, apiosk_continue |
| Retry interrupted discovery and adjust task options | apiosk_retry_search, apiosk_task_options, apiosk_source_selection, apiosk_analysis_quote |
| Saved answers, evidence, pages, downloads and conversations | apiosk_result, apiosk_evidence, apiosk_result_page, apiosk_artifact, apiosk_chats |
| Follow up using purchased evidence | apiosk_follow_up |
| Connected app actions and recurring checks | Integration/action review tools, native recurring tools and apiosk_schedule_handoff |
apiosk_ask defaults to mode: "sources". Automatic planning is available with mode: "automatic". Preparation never approves a purchase. Review the returned currency, maximum total, sources, gaps, expiry and approval ID before authorizing execution. The visible choices use the same purchasability filter as the Ask page; discovery metadata and source options are not purchased findings.
Results retain source dates, citations, coverage and gaps, including meaningful 0 and false values. Local filters, sorting, chart/table views, saved pages and exports reuse saved data. Follow-ups use purchased evidence where possible; a need for new data creates a separately reviewed request.
Run from this checkout
Requires Node.js 22.16 or newer and an authorized Apiosk connection. In this workspace the canonical directory is /Users/olivier/Documents/Apiosk/Production/Main/mcp.
cd /Users/olivier/Documents/Apiosk/Production/Main/mcpnpm ci npm run check npm test
Use the existing Apiosk credentials in your private environment or local .env; do not put credentials in committed examples. Runtime entry points read environment variables. To load .env explicitly, use Node's --env-file option.
| Entry point | Purpose |
|---|---|
node index.mjs / npm run start:stdio | Local stdio MCP; uses the configured connection token. The apiosk, apiosk-mcp and apiosk-mcp-server package commands use this entry. |
node server.mjs / npm start | Canonical hosted HTTP server, default port 3000, with OAuth metadata, registration, authorization and token routes. Also retains authenticated legacy SSE endpoints. |
node bin/mcp-2.mjs --http --host 127.0.0.1 --port 3012 | Minimal bearer-token HTTP transport for local testing. This compatibility filename remains internal; this entry does not provide the hosted OAuth flow. |
For stdio with a private .env:
node --env-file=.env index.mjsThe hosted server preserves the existing OAuth identity and secret configuration. Starting it requires those settings, including its signing secret; use node --env-file=.env server.mjs when they are in a local file. HTTP clients authenticate each request themselves. A server-wide token is never lent to HTTP callers. /health reports process health, not Gateway or source readiness.
Local tester
The tester runs at http://127.0.0.1:3013 and defaults to an MCP endpoint at http://127.0.0.1:3012/mcp. Start the minimal local MCP transport in one terminal:
node --env-file=.env bin/mcp-2.mjs --http --host 127.0.0.1 --port 3012Start the tester in another:
npm run dev:chatTo test the canonical hosted server on port 3000 instead:
MCP_DEV_URL=http://127.0.0.1:3000/mcp npm run dev:chatThe tester reads this checkout's .env, .env.v2.local and .env.dev.local, with inherited environment values taking precedence. It reuses an existing MCP_DEV_TOKEN and OPENROUTER_API_KEY. If no local OpenRouter key is set, it reads only the provider key from the sibling gateway/.env (OPENROUTER_API_KEY, then INTENT_API_KEY). It does not inherit Gateway execution flags or change those credentials. MCP_DEV_PORT, MCP_DEV_URL and MCP_DEV_MODEL override the tester defaults. Set MCP_DEV_GATEWAY_URL for a custom Gateway event origin; the embedded card and tester use the same fixed origin policy for live status updates.
Connect the intended account before asking a question. The tester calls apiosk_ask for the first question and renders the same embedded components served to other hosts. An initial discovery stops at the authoritative Ask card without an extra model-written answer. Later model continuations receive a bounded projection of tool results; full card data stays available to the component. Model API usage and approved source purchases are separate operations.
Connect Claude or Codex
Use examples/codex.toml, examples/claude-code.mcp.json or examples/claude-desktop.json, preserving other configured servers. Adjust absolute paths for your installation and keep tokens in private configuration or environment variables. These files are examples, not an installed connection.
The hosted connector address remains https://mcp.apiosk.com/mcp; local source changes do not update that deployment. The Apiosk plugin supplies Ask-first instructions and the hosted connection definition. server.json, manifest.json and dxt.json describe the canonical package; a desktop manifest is not a built or installed bundle.
Configuration and backend boundaries
| Variable | Meaning |
|---|---|
APIOSK_GATEWAY_V2_URL | Data/execution Gateway; defaults to https://gateway.apiosk.com. Use loopback HTTP only for a local Gateway. |
APIOSK_GATEWAY_URL | Existing OAuth agent gateway setting; it does not select the data/execution Gateway. |
APIOSK_CONNECT_TOKEN | Apiosk agent connection credential for stdio. |
APIOSK_TOKEN | Overrides the connection token. A valid personal App session JWT enables account-only routes; this server does not refresh that App session. |
APIOSK_WORKSPACE_ID | Stdio workspace. HTTP callers use x-apiosk-workspace-id. |
APIOSK_MCP_STATE_DIR | Persistent private journal directory; defaults to .local/state in the package. |
APIOSK_MCP_PORT / PORT | HTTP port; defaults to 3000. |
APIOSK_MCP_HOST / APIOSK_MCP_BIND_HOST | Listener address. The hosted entry defaults to 0.0.0.0; use loopback for local-only access. |
APIOSK_MCP_ALLOWED_HOSTS, APIOSK_MCP_ALLOWED_ORIGINS | Explicit host/origin controls for the HTTP listener. |
Gateway scope, budget, workspace and feature restrictions remain authoritative. Organization API keys are not substitutes for agent connection tokens in the raw task/approval protocol. Account-only integrations and native recurring operations may require a valid App session and backend enablement; an app_only or public_api_required response is not bypassed.
Connection tokens use /v2/ask/page, which applies the Ask page's interpreter, validation and source searches. App sessions use the original App routes. Both use the same source filtering, grouping, input values and display currency. Connected discovery preserves the App's matches without the older public API's interpretation repairs or extra source expansion; signed searches remain bound to the account, connection and workspace. Source refresh reuses the saved parse, and automatic planning adopts that displayed search without parsing the question again.
Recurring execution needs its own explicit review of the workflow, schedule, destination and cost limits. apiosk_schedule_handoff supplies instructions for the host scheduler and reports schedule_created: false; it does not create a scheduled job. External app actions likewise require their own reviewed execution.
Saved state, recovery and deployment
The journal stores private conversations, evidence and approval intent with private file permissions, without storing credentials. Conversations are separate from the web app's chat-history table; authorized Gateway tasks can be imported by ID. State scopes include the Gateway and workspace. Raw bearer callers are token-scoped; hosted OAuth sessions retain their verified grant scope across token refresh.
Atomic writes and per-request locks record approval intent before dispatch. An uncertain purchase is not blindly replayed: read saved status and use the returned recovery path. The quoted total is a spending ceiling across providers, not an all-or-nothing transaction. Local disk failures stop money-moving actions.
Hosted operation requires a persistent journal. The Fly configuration preserves the existing app identity and expects an existing mcp_state volume mounted at /data; run one machine until shared state and distributed locking are implemented. Provision and review that volume before deploying. See deployment and release instructions.
Pushing the repos
Only the beginning is shown; read the rest in the repo