MCP Servers

A collection of Model Context Protocol servers, templates, tools and more.

An MCP for Claude Code and Co-Work to allow you to interact with Flipsuite features in Claude. Create a Quest, get user info, and more.

Created 6/16/2026
Updated about 17 hours ago
Repository documentation and setup instructions

flipsuite-mcp

A local Model Context Protocol (MCP) server for the FlipSuite Community API. It lets an MCP client such as Claude manage your FlipSuite Discord community — quests, points, treasury, and lookups — in plain language.

The server runs on your own machine and authenticates with your own FlipSuite Community API key. No hosting and no OAuth required.

  • 17 tools covering the full FlipSuite Community API
  • Works in Claude Code, Claude Desktop, and Claude Cowork (as a local MCP server or plugin)
  • Faithful, fully-typed input schemas (including the complete quest model)
  • Built-in 1 request/second rate limiting and clear error messages
  • Destructive actions (asset transfers, burns, balance changes) carry safety annotations

What it can do

| Area | Tools | |------|-------| | Quests | create_quest, get_quest, list_quests, get_quest_completions | | Points | list_point_systems, get_points_balance, update_points_balance | | Treasury (tipping) | get_tipping_wallet_balance, get_tipping_wallet_inventory, send_tip, transfer_asset, create_airdrop, create_raffle, burn_asset | | Lookups | get_user, get_user_flipwallets, get_supported_chains |

See docs/TOOLS.md for the full reference and docs/SAFETY.md for how the write/destructive tools behave.

Note: FlipSuite has no "update quest" endpoint, so quests can be created and read but not edited. Treasury writes (send_tip, transfer_asset, create_airdrop, create_raffle, burn_asset) and update_points_balance change real assets/balances — read the safety doc.

Asset-moving tools — where they work

Five tools move or destroy real on-chain assets: send_tip, transfer_asset, create_airdrop, create_raffle, and burn_asset. The server exposes them like any other tool, but whether the assistant will actually call them depends on the client's safety policy, not on this server.

  • Claude Code — executes the asset tools after showing a confirmation prompt. This is the smoothest place to run them in plain language ("tip user <id> 1 TOKEN on Cronos in channel <id>").
  • Claude Cowork — by design, the assistant declines to execute on-chain asset transfers even when you confirm. The read tools, create_quest, and points lookups work conversationally as expected, but for the five asset tools the assistant will hand the action back to you rather than send it.
  • Direct (no assistant) — the underlying actions are ordinary FlipSuite features; you can always perform them in the FlipSuite Discord bot or dashboard.

In short: reads, quests, and lookups are frictionless everywhere; the treasury writes are best run from Claude Code or the FlipSuite app, and you (not the assistant) remain the operator for anything that moves funds. See docs/SAFETY.md for the full breakdown.

Requirements

  • Node.js 18+ (nodejs.org — install the LTS build)
  • A FlipSuite Community API key — generate one in the FlipSuite dashboard under the Developer tab.

Get the code

git clone https://github.com/Beannation/flipsuite-mcp.git
cd flipsuite-mcp
npm install
npm run build

The repo ships with a prebuilt dist/, so the plugin install paths below work even without running the build yourself.

Install

The server reads your key from the FLIPSUITE_API_KEY environment variable in every case.

Claude Code

claude mcp add flipsuite -s user -t stdio \
  -e FLIPSUITE_API_KEY=YOUR_KEY \
  -- node "/absolute/path/to/flipsuite-mcp/dist/index.js"

-s user makes it available in every project. Confirm with claude mcp list, then ask Claude: "Use get_supported_chains to list FlipSuite's chains."

Claude Desktop

Edit claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/):

{
  "mcpServers": {
    "flipsuite": {
      "command": "node",
      "args": ["/absolute/path/to/flipsuite-mcp/dist/index.js"],
      "env": { "FLIPSUITE_API_KEY": "YOUR_KEY" }
    }
  }
}

Fully quit and relaunch Claude Desktop afterwards.

Claude Cowork

Cowork runs inside Claude Desktop, so use the same config file. Go to Settings → Developer → Edit Config, which opens claude_desktop_config.json (creating it if it doesn't exist), and add the same mcpServers block shown above under Claude Desktop. There is no separate "add a local MCP server" form — you edit the JSON directly. Save, fully quit and relaunch, then start a new chat (tools load when a chat starts). Alternatively, install it as a plugin from the Plugins settings page.

On managed/work accounts an admin may have disabled user-added local MCP servers. If the Developer config is locked or the server's tools never appear, use a personal account or ask your admin to deploy it as an organization plugin.

As a plugin (Cowork & Claude Code)

This repo is also a single-plugin marketplace named beannation:

/plugin marketplace add https://github.com/Beannation/flipsuite-mcp.git
/plugin install flipsuite-mcp@beannation

The plugin reads FLIPSUITE_API_KEY from the environment Claude launches it from.

Environment variables

| Variable | Required | Description | |----------|----------|-------------| | FLIPSUITE_API_KEY | yes | Your FlipSuite Community API key. | | FLIPSUITE_API_BASE_URL | no | Override the API base URL (default https://api.flipsuite.xyz). |

Example prompts

  • "List my FlipSuite point systems."
  • "Create a draft quest called 'Welcome' that requires following @flipsuitexyz on X, rewarding 100 XP to everyone."
  • "Show the top 10 holders of point system <id>."
  • "What tokens are in our tipping wallet on Base?"

Develop

npm install
npm run build      # compile TypeScript to dist/
npm run watch      # rebuild on change
npm start          # run the compiled server (needs FLIPSUITE_API_KEY)

Project layout: src/client.ts (transport-agnostic API client), src/schemas.ts + src/extended-schemas.ts (Zod input schemas), src/tools.ts + src/extended-tools.ts (tool registrations), src/index.ts (stdio entry point).

Notes & limits

  • The FlipSuite Community API is rate limited to 1 request/second; the server throttles to match.
  • All Community API endpoints require a valid key via the x-api-key header.
  • get_user requires the FlipSuite Growth plan.

Privacy

See PRIVACY.md. The server runs locally, stores nothing, and talks only to the FlipSuite API using the key you provide.

Contributing

See CONTRIBUTING.md.

License

MIT — see LICENSE.

Quick Setup
Installation guide for this server

Install Package (if required)

npx @modelcontextprotocol/server-flipsuite-mcp

Cursor configuration (mcp.json)

{ "mcpServers": { "beannation-flipsuite-mcp": { "command": "npx", "args": [ "beannation-flipsuite-mcp" ] } } }