jaicp-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JAICP_ENV | No | Path to a .env file with these variables. If not set, defaults to .env in server cwd. | |
| JAICP_HOST | No | Base URL of JAICP API. Default: https://app.jaicp.com | https://app.jaicp.com |
| JAICP_NLP_TOKEN | No | Token for CAILA Direct API, substituted into {accessToken} in path. | |
| JAICP_CALLS_TOKEN | No | Token for Dialer calls API, substituted into {token} in path. | |
| JAICP_UNIFIED_TOKEN | No | Token for bot-channel, project, reporter, async, text-campaign APIs (Authorization: Bearer). | |
| JAICP_PROJECT_SHORT_NAME | No | Project short name used as a query parameter if an operation has it. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jaicp_specsA | Official JAICP/Tovie OpenAPI specs this MCP was built from. No network. |
| jaicp_operationsA | List OpenAPI operations from one spec. Optional search over operationId, path, summary. |
| jaicp_callB | Call a JAICP/Tovie OpenAPI operation by spec id + operationId. Writes need confirm=true unless JAICP_READ_ONLY. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
The three tools occupy clearly separate roles: jaicp_specs exposes available API specifications, jaicp_operations lists operations within a spec, and jaicp_call invokes a specific operation. There is no meaningful semantic overlap between them.
All tools share the jaicp_ prefix and use lowercase snake_case, making them predictable. The names are not strictly verb_noun — jaicp_specs and jaicp_operations are resource-style nouns while jaicp_call is a verb — but the convention is still clear.
Three tools is the right size for a dynamic OpenAPI gateway: one for spec discovery, one for operation discovery, and one for execution. Each tool is essential and none is redundant.
This covers the full workflow for the domain: discover available specs, inspect and search operations, and call any operation. Since jaicp_call can target any operationId, the entire API surface is reachable without needing per-endpoint tools.