Query channels, search messages, and read threads, users and reactions in your Stream Chat app. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"stream": {
"url": "https://stream.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"stream": {
"type": "http",
"url": "https://stream.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Stream API key and Stream API secret.
Find both in the Stream dashboard → App → API keys. Your key and secret are used only to call the API on your behalf (the secret signs a server-side token) and to derive a private account id; they are never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Stream API key and Stream API secret. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Stream connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
stream_get_app | read | Get app settings Fetch the Stream app's settings and configured channel types. Good first call to confirm credentials and discover available channel types. GET /api/v2/app. |
stream_query_channels | read | Query channels List/filter channels by a Stream query filter. e.g. filter {"type":"messaging"} or {"members":{"$in":["user-1"]}}. Returns channels with recent state. POST /api/v2/chat/channels. |
stream_get_channel | read | Get channel state + recent messages Fetch a single channel's state (config, members) and its most recent messages. Note: uses Stream's get-or-create endpoint — for an existing channel it reads; if the type/id does not exist it may be created empty. POST /api/v2/chat/channels/{type}/{id}/query. |
stream_search_messages | read | Search messages Search messages across channels. Scope with a channel filter (filter, e.g. {"type":"messaging"}) plus EITHER a full-text `query` OR a `message_filter` object (e.g. {"text":{"$q":"refund"}}). GET /api/v2/chat/search. |
stream_get_message | read | Get a message Fetch a single message by its id. GET /api/v2/chat/messages/{id}. |
stream_get_replies | read | Get thread replies Fetch the reply messages in a thread, given the parent message id. GET /api/v2/chat/messages/{parent_id}/replies. |
stream_get_reactions | read | Get message reactions List the reactions on a message. GET /api/v2/chat/messages/{id}/reactions. |
stream_query_members | read | Query channel members List/filter the members of one channel. Requires the channel type + id. Optional member filter, e.g. {"name":{"$autocomplete":"jo"}}. GET /api/v2/chat/members. |
stream_query_users | read | Query users List/filter users in the app. e.g. filter {"role":{"$eq":"admin"}} or {"id":{"$in":["u1"]}}. GET /api/v2/users. |
stream_query_threads | read | Query threads List threads (messages with replies). Server-side calls should pass a user_id to scope thread read-state to that user. POST /api/v2/chat/threads. |
stream_get_unread_counts | read | Get unread counts for a user Fetch total and per-channel unread message/mention counts for one user. GET /api/v2/chat/unread. |
stream_send_message | write | Send a message (WRITE — posts to Stream) ⚠️ WRITE: post a new message to a channel, attributed to user_id (must be an existing user in the app). POST /api/v2/chat/channels/{type}/{id}/message. |
stream_send_reaction | write | Send a reaction (WRITE — posts to Stream) ⚠️ WRITE: add a reaction (e.g. "like", "love") to a message, attributed to user_id (must be an existing user). POST /api/v2/chat/messages/{id}/reaction. |
stream_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
stream_request_feature | Request a missing feature Tell usefulapi that the user needs something the Stream tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
stream_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Stream tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
stream_cancel_subscription | Cancel the Pro subscription Cancel the caller's Stream Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run stream_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Pro | $9/mo · $90/yr | Unlimited |
Pro covers this Stream server only. Subscribe with stream_upgrade (it returns a Stripe Checkout link). Cancel any time with stream_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running stream_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Stream. The server calls the Stream API with your own Stream access, so it sees only the data that your account can see.
The login page asks for your Stream API key and Stream API secret. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Stream API key and Stream API secret. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Stream API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Stream.
Yes, if you approve it. 2 of the 13 Stream tools can create or change data. The other 11 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Stream server only. Run stream_usage_status to see how many calls you used.
Ask the AI to run stream_upgrade: it returns a Stripe Checkout link. To cancel, run stream_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with stream_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.