intakeq-mcp
by oktopeak
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP server port (HTTP mode only) | 3000 |
| TRANSPORT | No | Transport mode: stdio or http | stdio |
| MCP_API_KEY | No | Bearer token to gate the HTTP /mcp endpoint. Required in HTTP mode unless MCP_ALLOW_NO_AUTH=true | |
| MCP_BASE_URL | No | Base URL printed in HTTP startup logs | http://127.0.0.1:3000 |
| INTAKEQ_API_KEY | No | Fallback API key for CI / headless use (prefer the set_api_key tool) | |
| INTAKEQ_API_BASE | No | Override the IntakeQ API base URL | https://intakeq.com/api/v1 |
| MCP_ALLOW_NO_AUTH | No | Set to true to explicitly allow HTTP mode without MCP_API_KEY (local dev only) |
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/oktopeak/IntakeQ'
If you have feedback or need assistance with the MCP directory API, please join our Discord server