AKBridge MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HTTP_PROXY | No | Standard HTTP proxy URL. | |
| HTTPS_PROXY | No | Standard HTTPS proxy URL. | |
| AKBRIDGE_NO_PROXY | No | AKBridge-specific no-proxy list. | |
| AKBRIDGE_ALL_PROXY | No | AKBridge-specific proxy for all protocols. | |
| AKBRIDGE_CACHE_TTL | No | Cache time-to-live in seconds for read-only interfaces. | |
| AKBRIDGE_JSON_LOGS | No | Set to '1' to write retry diagnostics as JSON Lines to stderr. | |
| AKBRIDGE_HTTP_PROXY | No | AKBridge-specific HTTP proxy URL. | |
| AKBRIDGE_HTTPS_PROXY | No | AKBridge-specific HTTPS proxy URL. | |
| AKBRIDGE_CALL_TIMEOUT | No | Timeout for AKShare calls in seconds. | |
| AKBRIDGE_MAX_ATTEMPTS | No | Maximum number of retry attempts. | |
| AKBRIDGE_RATE_LIMIT_SECONDS | No | Rate limit interval in seconds. | |
| AKBRIDGE_CIRCUIT_FAILURE_THRESHOLD | No | Circuit breaker failure threshold. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| akbridge_searchA | Search the local AKShare semantic catalog and return a small RAG context. Always call this before akbridge_call when the user describes data in natural language; never guess interface names. |
| akbridge_describeA | Describe one AKShare interface, including parameters, signature, return metadata, side_effect flag, and a safe example call. Use this to confirm a name returned by akbridge_search before calling it. |
| akbridge_callA | Resolve and call one AKShare interface with deterministic output controls (output_mode, page, page_size). Interfaces flagged side_effect=true mutate global state or credentials and require explicit user authorization before invocation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| akbridge.query_financial_data | End-to-end workflow: search the AKShare catalog, describe the matching interface, then call it with structured output. |
| akbridge.describe_api | Return the canonical schema, signature, parameters, return type and example call for one AKShare interface. |
| akbridge.search_catalog | Lexical, deterministic search over the AKShare catalog. Use this before inventing an interface name. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| akbridge-skill | Deterministic instructions for searching and calling AKBridge. |
| akbridge-metrics | Process-local AKBridge call counters and durations. |
TDQS
Scored across 3 tools
Each tool has a distinct role in a clear discovery-to-invocation pipeline: search finds candidate interfaces, describe confirms metadata, and call executes. The descriptions explicitly state ordering and boundaries, leaving no overlapping purpose.
All tools follow a consistent akbridge_ prefix plus a concise verb/noun pattern: search, describe, call. The convention is predictable and easy to scan.
Three tools are tightly scoped to the server's purpose of safely resolving and calling AKShare interfaces. Each tool earns its place, and adding more would likely add confusion rather than capability.
The surface covers the key lifecycle: discover via search, verify via describe, and execute via call. Minor gaps exist, such as no explicit browse/list-all or batch-invocation operation, but agents can work around these through search.