home / mcp / developer mcp server

Developer MCP Server

Provides access to multiple MCP servers for resources, prompts, and tools across ElizaOS

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "fleek-platform-eliza-plugin-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-github"
      ],
      "env": {
        "GOOGLE_MAPS_API_KEY": "<YOUR_API_KEY>",
        "GITHUB_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>"
      }
    }
  }
}

The MCP (Model Context Protocol) plugin connects your ElizaOS agents to multiple MCP servers, letting them access resources, prompts, and tools from those servers. This enables your agents to reference external data, follow templated workflows, and execute external capabilities in a coordinated way across several MCP endpoints.

How to use

You can configure your agents to connect to multiple MCP servers and then use the servers’ resources, prompts, and tools in your conversations. Each server provides a scoped set of capabilities you can reference during a session. When an agent needs data or a specialized action, it can query the available MCP servers, select an appropriate tool or prompt, and run it to obtain results or trigger workflows. The plugin exposes the servers you configure so your agent can discover and use their capabilities automatically, and you can mix multiple servers for richer behavior.

How to install

Prerequisites: ensure you have Node.js installed (version 12+ is recommended). You may also want pnpm or yarn for your preferred package manager.

Install the MCP plugin package for your ElizaOS project using your package manager of choice.

# npm
npm install @fleek-platform/eliza-plugin-mcp

# pnpm
pnpm install @fleek-platform/eliza-plugin-mcp

# yarn
yarn add @fleek-platform/eliza-plugin-mcp

# bun
bun add @fleek-platform/eliza-plugin-mcp

Additional setup instructions and examples

Configure your character to include the MCP plugin and define the MCP servers you want to connect to. You can mix several stdio servers (local commands) to run MCP servers alongside each other. Each server can provide a different set of resources, prompts, and tools.

Example of a character configuration that enables MCP servers. This shows three stdio servers started via npx with different MCP server packages.

{
  "name": "Developer Assistant",
  "plugins": ["@elizaos/plugin-mcp", "other-plugins"],
  "settings": {
    "mcp": {
      "servers": {
        "github": {
          "command": "npx",
          "args": ["-y", "@modelcontextprotocol/server-github"],
          "env": {
            "GITHUB_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>"
          }
        },
        "puppeteer": {
          "command": "npx",
          "args": ["-y", "@modelcontextprotocol/server-puppeteer"]
        },
        "google_maps": {
          "command": "npx",
          "args": ["-y", "@modelcontextprotocol/server-google-maps"],
          "env": {
            "GOOGLE_MAPS_API_KEY": "<YOUR_API_KEY>"
          }
        }
      },
      "maxRetries": 2
    }
  }
}