Tiny MCP Server

Test MCP server with example tools for integration testing

Local serverstdioTypeScript

What is the Tiny MCP server?

Test MCP server with example tools for integration testing. Exposed over MCP by the tiny mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Power your favorite coding agents (Claude Code, Codex, OpenCode, and more) with your Poe subscription—no need to handle multiple providers/accounts. Poe Code routes everything through the Poe API .

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at poe-code on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Configuration

You will need 2 environment variables: POE_API_KEY, POE_BASE_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Tiny's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the tiny mcp server does with a few real requests.

How to install the Tiny MCP server

{
  "mcpServers": {
    "test-2": {
      "command": "npx",
      "args": ["-y", "poe-code"],
      "env": {
        "POE_API_KEY": "your-value",
        "POE_BASE_URL": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
POE_API_KEYCredential the server authenticates with.Yes
POE_BASE_URLEndpoint or connection string the server talks to.Yes

Frequently asked questions

It connects Tiny to MCP-compatible AI assistants such as Claude and Cursor. Instead of copying data back and forth by hand, the assistant works with Tiny directly.