Invoker MCP Server
⚡ Invoker MCP 서버
AI 에이전트가 .ivk 형식의 HTTP 요청을 생성, 실행 및 관리하도록 합니다.
ivkjs를 래핑하여 AI 도구가 Invoker API 클라이언트와 상호 작용할 수 있게 해주는 MCP(Model Context Protocol) 서버입니다.
설치
npm install -g invoker-mcpRelated MCP server: Swagger/Postman MCP Server
구성
Claude Desktop
~/Library/Application Support/Claude/claude_desktop_config.json에 추가하세요:
{
"mcpServers": {
"invoker": {
"command": "npx",
"args": ["invoker-mcp"]
}
}
}Claude Code
claude mcp add invoker -- npx invoker-mcp도구
도구 | 설명 |
| 폴더에서 .ivk 및 .md 파일 스캔 |
| .ivk 파일 읽기 및 파싱 |
| 새 .ivk 요청 파일 생성 |
| 요청 실행 (파일 또는 인라인에서) |
| 변수가 포함된 모든 환경 나열 |
| 환경 변수 설정 |
| 활성 환경 전환 |
| 새 환경 생성 |
| 정적 문서 사이트 구축 |
사용 예시 (AI 대화 중)
"./invoker에 있는 내 API 컬렉션을 스캔하고 로그인 요청을 보내줘"
AI 에이전트는 다음과 같이 수행합니다:
folder_path: "./invoker"와 함께invoker_list_collection호출file_path: "./invoker/auth/login.ivk"와 함께invoker_send_request호출응답을 사용자에게 반환
라이선스
MIT
Available Tools
9 toolsinvoker_add_environmentAdd EnvironmentA
Create a new environment with optional initial variables.
Inputs: name (required), variables.
invoker_build_siteBuild Documentation 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.
Inputs: collection_path (required), output_path, title.
invoker_create_requestCreate 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.
Inputs: file_path (required), method (required), url (required), name, +7 more.
invoker_list_collectionList CollectionARead-only
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.
Inputs: folder_path (required).
invoker_list_environmentsList EnvironmentsARead-only
List all environments with their variables. Shows which environment is currently active. Use this to see available environments before switching or setting variables.
Inputs: no named parameters.
invoker_read_requestRead RequestARead-only
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.
Inputs: file_path (required).
invoker_send_requestSend 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.
Inputs: file_path, method, url, headers, +1 more.
invoker_set_variableSet VariableAIdempotent
Set an environment variable in the active environment. The variable will be used to resolve {{name}} placeholders in subsequent requests.
Inputs: name (required), value (required).
invoker_switch_environmentSwitch EnvironmentAIdempotent
Switch the active environment by name or index. All subsequent variable resolution will use the new environment's values.
Inputs: environment (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
AI-callable tools for API mocking, testing, monitoring, security, and automation.
Discover, compare, route, and execute machine-accessible capabilities for AI agents.
Pay-per-call tools for AI agents, paid in USDC on Base or Solana. Web search, page and PDF reading, crypto news, Hyperliquid perps, market pulse, Chainlink price history, token checks, SEC filings, weather and more. Free calls every day, and a failed call costs nothing. Works with Tollkit Wallet.
Discover, inspect and run 63,000+ agent tools from one balance. Pay per call, no subscriptions.
Related MCP Servers
- FlicenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to interact with Istek API Client for managing workspaces, collections, environments, variables, and request history. Allows natural language control of API development workflows including creating collections, adding requests, and managing environment configurations.-
- FlicenseNot gradedqualityNot gradedmaintenanceEnables AI agents to dynamically discover and interact with APIs through Swagger/OpenAPI specifications and Postman collections using a strategic four-tool approach. It streamlines API integration by providing universal tools for endpoint discovery, detailed request information, and authenticated execution.1-
- AlicenseCqualityBmaintenanceEnables AI agents to create, manage, and execute API collections, requests, and environments in Insomnia-compatible formats. It supports direct synchronization with the local Insomnia app database and importing from OpenAPI, Postman, and cURL.30175 npm27MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to inspect, test, validate, compare, and debug HTTP APIs through a structured toolkit, with features such as secret redaction, response contract validation, regression comparison, health checks, and incident investigation workflows.MIT