Apiosk MCP Server
by obcraft
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIOSK_HOME | No | Override the default ~/.apiosk directory | |
| APIOSK_GATEWAY | No | Override the gateway base URL | |
| APIOSK_USER_JWT | No | Unlock dashboard wallet routes (alternative to APIOSK_DASHBOARD_JWT) | |
| APIOSK_X_PAYMENT | No | Attach a pre-built x402 proof manually | |
| APIOSK_PRIVATE_KEY | No | Enables automatic x402 settlement and signed publish requests | |
| APIOSK_CONNECT_TOKEN | No | Attach a dashboard-managed connect token | |
| APIOSK_DASHBOARD_JWT | No | Unlock dashboard wallet routes (alternative to APIOSK_USER_JWT) | |
| APIOSK_DASHBOARD_URL | No | Override the human-facing dashboard/app URL | https://dashboard.apiosk.com |
| APIOSK_PROVIDER_TOKEN | No | Provider token for publishing tools (sk_live_...) | |
| APIOSK_WALLET_ADDRESS | No | Send a wallet address for wallet-aware flows | |
| APIOSK_MCP_AUTH_SECRET | No | Alternative to APIOSK_MCP_OAUTH_SECRET | |
| APIOSK_MCP_NPM_PACKAGE | No | Override the npm package spec for the PyPI launcher | |
| APIOSK_MCP_BEARER_TOKEN | No | Optional hosted OAuth access token used by the live scripts for authenticated protected-tool checks | |
| APIOSK_MCP_OAUTH_SECRET | No | Signing secret for hosted OAuth codes, access tokens, and refresh tokens | |
| APIOSK_MCP_WALLET_STORE | No | Override the local wallet store path | |
| APIOSK_CONTROL_PLANE_URL | No | Override the MCP-owned control-plane API base URL | https://mcp.apiosk.com |
| APIOSK_CONNECT_HEADER_NAME | No | Override the connect-token header name | |
| APIOSK_ENABLE_LOCAL_WALLETS | No | Enable local wallet tools in HTTP server mode | |
| APIOSK_CONNECT_AUTHORIZATION | No | Custom Authorization header |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/obcraft/apiosk-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server