MCP Server (Agents)

FloatMessage ships a hosted Model Context Protocol server so AI agents (Claude, IDE assistants, custom agents) can manage your account as native tools - create messages, edit landing pages, update the knowledge base, read analytics, and reply to chats.

Endpoint

https://floatmessage.com/api/mcp

It speaks the MCP Streamable HTTP transport (JSON-RPC 2.0 over POST) and is stateless. Authenticate with the same API key as the REST API, sent as a Bearer token.

Connect from Claude Code / Desktop

Add it as a remote MCP server with an Authorization header:

claude mcp add --transport http floatmessage \
  https://floatmessage.com/api/mcp \
  --header "Authorization: Bearer fm_live_YOUR_KEY"

Or, in a client that uses a JSON config:

{
  "mcpServers": {
    "floatmessage": {
      "type": "http",
      "url": "https://floatmessage.com/api/mcp",
      "headers": { "Authorization": "Bearer fm_live_YOUR_KEY" }
    }
  }
}

Available tools

The tool set mirrors the REST resources one-to-one. Call tools/list for the live, fully-typed schema. Highlights:

• whoami - account, plan, primary domain
• list_messages, create_message, update_message, delete_message
• list_landing_pages, create_landing_page, publish_landing_page
• list_domains, create_domain
• list_knowledge, create_knowledge
• get_analytics, list_form_submissions, list_survey_responses
• list_conversations, send_chat_message

Domain-scoped tools take an optional domain argument (hostname or UUID), defaulting to your primary domain.

Raw JSON-RPC example

# List available tools
curl -X POST https://floatmessage.com/api/mcp \
  -H "Authorization: Bearer fm_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

# Call a tool
curl -X POST https://floatmessage.com/api/mcp \
  -H "Authorization: Bearer fm_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call",
       "params":{"name":"list_messages","arguments":{}}}'