Skip to main content
Glama
doossee
by doossee
README.md
<div align="center">

# ⚡ Invoker MCP Server

**Let AI agents create, run, and manage HTTP requests in .ivk format.**

[![npm](https://img.shields.io/npm/v/invoker-mcp.svg?style=flat-square)](https://www.npmjs.com/package/invoker-mcp)
[![License: MIT](https://img.shields.io/badge/license-MIT-green.svg?style=flat-square)](LICENSE)

</div>

---

An MCP (Model Context Protocol) server that wraps [ivkjs](https://github.com/doossee/ivkjs) to let AI tools interact with the [Invoker](https://github.com/doossee/invoker-app) API client.

## Install

```bash
npm install -g invoker-mcp
```

## Configure

### Claude Desktop

Add to `~/Library/Application Support/Claude/claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "invoker": {
      "command": "npx",
      "args": ["invoker-mcp"]
    }
  }
}
```

### Claude Code

```bash
claude mcp add invoker -- npx invoker-mcp
```

## Tools

| Tool | Description |
|---|---|
| `invoker_list_collection` | Scan a folder for .ivk and .md files |
| `invoker_read_request` | Read and parse an .ivk file |
| `invoker_create_request` | Create a new .ivk request file |
| `invoker_send_request` | Execute a request (from file or inline) |
| `invoker_list_environments` | List all environments with variables |
| `invoker_set_variable` | Set an environment variable |
| `invoker_switch_environment` | Switch the active environment |
| `invoker_add_environment` | Create a new environment |
| `invoker_build_site` | Build a static documentation site |

## Example usage (in an AI conversation)

> "Scan my API collection at ./invoker and send the login request"

The AI agent would:
1. Call `invoker_list_collection` with `folder_path: "./invoker"`
2. Call `invoker_send_request` with `file_path: "./invoker/auth/login.ivk"`
3. Return the response to you

## License

MIT

TDQS

A4.2/5.0

Scored across 9 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness4/5

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

ActivityInactive
ResponsivenessNo issues