MCP Server

Pie.host runs a hosted MCP server at https://piehost.com/mcp. Connect it to an MCP-compatible AI like ChatGPT or Claude and it can read your account info, list your resources (PieSocket, PieDB, PieApp, and the rest of the lineup), pull live stats, and search Pie.host's documentation, all inside the chat, without you copying API keys around.

Authentication

The server sits behind the same OAuth 2.0 login you already use for Pie.host. Connecting an MCP client redirects you to a normal Pie.host sign-in and consent screen, where you authorize the client to read your account and resource information. It only ever needs the mcp:read scope, there's no write scope yet, so every tool is read-only: nothing an MCP client does through this server can change your resources, billing, or settings.

Every tool is also scoped to your own account. A resource id that doesn't belong to you simply comes back as "not found", there's no way for a tool call to see another user's data.

Requests are rate-limited to 60 per minute per account.

Tools

The server exposes five tools.

getaccountinfo

Returns the authenticated user's profile, no parameters needed.

Returns: id, name, username, email, email_verified, avatar.

get_resources

Lists your resources across every Pie product (PieSocket, PieDB, PieGres, PieMongo, PieCache, PieBucket, PieBox, PieMail, PieMonitor, PieApp, and PieSocket on-prem licenses).

Parameter Type Required Description
resource_type string No Filter to one type: channel (PieSocket), piedb, piegres, piemongo, piecache, piebucket, piebox, piemail, piemonitor, pieapp, piesocketonpremlicense.

Returns: an array of {id, resource_type, name, hourly_rate, created_at}.

getresourcestats

Fetches live stats for one resource from get_resources, the data returned depends on the resource type.

Parameter Type Required Description
id integer Yes Resource id, from get_resources.
api_key string No For PieSocket channels with multiple API keys, picks which key's stats to return. Defaults to the first-created key.

Returns:

  • PieSocket channels: active_connections, peak_connections_today, messages_today, presence_members, a message breakdown (inbound/outbound/publish_api), today's billing snapshot (sent_messages, peak_connections, quota_used_percentage, bill, extra_messages), and which api_key was used (plus other_api_keys if the channel has more than one).
  • PieMonitor: last_status, last_message, last_latency_ms, last_checked_at.
  • Everything else (PieDB, PieGres, PieMongo, PieCache, PieBucket, PieBox, PieMail, PieApp, on-prem licenses): a note saying live stats aren't available yet for that type.

list_docs

Returns an index of every published Pie.host documentation article (this one included), no parameters needed. Call this first to find the right article, then pass its id to get_doc.

Returns: an array of {id, category, title, description}.

get_doc

Fetches the full content of one or more documentation articles by id.

Parameter Type Required Description
ids array of integers Yes Article ids, from list_docs.

Returns: the plain-text content of each requested article.

Connecting a client

Any other MCP-compatible client can connect the same way, point it at https://piehost.com/mcp and complete the OAuth consent screen.