Invoker MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| invoker_list_collectionA | Scan a folder for .ivk request files and .md documentation files. Returns the file tree with counts. Use this to discover what requests and docs exist in a collection. |
| invoker_read_requestA | Read and parse an .ivk file. Returns the parsed request with method, URL, headers, body, directives, and scripts. Use this to inspect what a request does before sending it. |
| invoker_create_requestA | Create a new .ivk request file. Specify the HTTP method, URL, and optionally headers, body, auth, scripts. The file is written to disk in .ivk format. |
| invoker_send_requestA | Execute an HTTP request from an .ivk file or inline params. Resolves {{variables}} from the active environment, runs pre/post scripts, and returns the full response with status, headers, body, test results, and console logs. |
| invoker_list_environmentsA | List all environments with their variables. Shows which environment is currently active. Use this to see available environments before switching or setting variables. |
| invoker_set_variableA | Set an environment variable in the active environment. The variable will be used to resolve {{name}} placeholders in subsequent requests. |
| invoker_switch_environmentA | Switch the active environment by name or index. All subsequent variable resolution will use the new environment's values. |
| invoker_add_environmentA | Create a new environment with optional initial variables. |
| invoker_build_siteA | Build a static documentation site from an Invoker collection folder. Produces a deployable dist/ with markdown docs and inline runnable .ivk request widgets. Requires the invoker-app to be installed. |
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 9 tools
Each tool has a clearly distinct purpose with no overlap: creating environments, building sites, creating/reading/sending requests, listing collections/environments, and managing variables. The descriptions clearly differentiate their functions, preventing misselection.
All tools follow a consistent 'invoker_verb_noun' pattern (e.g., invoker_add_environment, invoker_build_site). This predictable naming makes it easy for agents to understand and navigate the toolset without confusion.
With 9 tools, the server is well-scoped for managing Invoker collections, environments, and requests. Each tool serves a specific role in the workflow, from setup to execution, without being overly sparse or bloated.
The toolset covers core CRUD and lifecycle operations for environments, variables, and requests, with good workflow support. A minor gap exists in lacking tools for deleting or updating environments/requests, but agents can work around this with file system operations.