Intelliverse Router MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KB_BASE_URL | No | Optional override for knowledge base URL. | |
| EDGE_BASE_URL | No | Optional override for edge base URL. | |
| ROUTER_API_KEY | Yes | Your API key from Workspace → API Keys. | |
| ROUTER_WORKSPACE_ID | Yes | Your workspace UUID. | |
| ROUTER_MANAGEMENT_KEY | Yes | Your management key from Account → Management Keys. |
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 |
|---|---|
| chatA | Send a chat completion. Never name an LLM — omit |
| list_modelsA | List the tier aliases your API key can call. These are the only model strings that exist. |
| get_creditsB | LLM daily budget for the API key plus per-App-ID media credit wallets (image, video, voice, audio, audiobook, 3D). |
| create_appB | Create an app (the entry point for knowledge bases, credit wallets, and per-app cost tracking). Returns the app id and a recommended tier based on the declared workload. |
| list_appsC | List apps in the workspace with their recommended tiers and routing profiles. |
| create_api_keyA | Mint a tier API key (air | pro | pro_max), optionally bound to an App ID and daily spend limit. The raw key is returned exactly once — store it. |
| list_api_keysA | List API keys (prefixes only) with tier, app binding, and spend limits. |
| revoke_api_keyC | Permanently delete an API key by id. |
| kb_ingestA | Add documents (raw text or URLs — URLs are scraped) to the app's pgvector knowledge base. Chunks are embedded and become searchable memory for that App ID. |
| kb_searchB | Semantic search over the app's chunks. Returns matches with similarity scores. |
| kb_chatA | RAG chat: retrieves relevant chunks for the App ID and answers with [doc:id] citations. |
| kb_documentsB | List documents ingested for an App ID. |
| send_emailA | Send transactional/newsletter email through the platform email engine (Pro plan+). Billed at the email.send10 SKU from the App ID's iv_credits wallet (hold → dispatch → settle); failed sends are never charged and partial batches settle on accepted recipients only. |
| generate_mediaA | Generate image | video | voiceover | audio (music/sfx) | gen3d assets. Credits are held from the App ID's wallet and settled on completion. Returns a job — poll with media_job_status. |
| media_job_statusC | Get status/output of a media generation job. |
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 15 tools
Each tool targets a distinct domain: knowledge base (kb_*), app management, chat, models/credits, API keys, email, and media generation. Overlaps are minimal and well-defined.
Most tools follow a verb_noun pattern with underscores. Slight inconsistency: 'kb_documents' is a noun phrase while others are verb phrases. Otherwise consistent.
15 tools is appropriate for the broad scope covering knowledge base, chat, media, email, and API management. Each tool serves a clear purpose without redundancy.
Core operations are present (create, ingest, search, generate), but missing update/delete for apps and documents, and no cancel for media jobs. Notable gaps for full lifecycle.