Stream MCP by usefulapi

Server Details

Query channels, search messages, and read threads, users and reactions in your Stream Chat app.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Healthy
Uptime: 70.5% over 54 days
Last Tested: 2026-10-10 19:17
Transport: Streamable HTTP · MCP 2025-06-18
URL
Repository: m190/usefulapi-mcp
GitHub Stars: 0

TDQS

A3.7/5.0

Scored 2026-09-10 22:49 across 13 tools

Disambiguation4/5

Most tools clearly target distinct resources or actions, and the get_/query_/search_ prefixes help separate single-resource fetches from filtered lists. The main ambiguity is between get_channel and query_channels, since both return channel state and recent messages, and get_replies vs query_threads both surface threaded conversations.

Naming Consistency5/5

All tools follow a consistent stream_ prefix with clear verb_noun snake_case names. get_ is used for direct lookups, query_ for filtered listings, search_ for full-text search, and send_ for write actions, making the naming pattern highly predictable.

Tool Count5/5

With 13 tools, the set is well-scoped for a Stream chat integration covering app config, channels, messages, reactions, members, threads, users, and search. Each tool corresponds to a meaningful API surface without excessive fragmentation.

Completeness2/5

The read side is fairly comprehensive, but the write surface is severely limited: there is no update/delete for messages or reactions, no channel management, and no member or user mutations. Agents can look up and send content but cannot edit, moderate, or manage the chat environment, which is a significant gap for a chat API server.

Available Tools

13 tools

stream_get_appGet app settings

Read-only

Inspect

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.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

stream_get_channelGet channel state + recent messages

Read-only

Inspect

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.

ParametersJSON Schema

Name	Required	Description
`id`	Yes	Channel id (the part after the type).
`type`	Yes	Channel type, e.g. "messaging", "team", "livestream".
`messages_limit`	No	Recent messages to return. Default 25.

stream_get_messageGet a message

Read-only

Inspect

Fetch a single message by its id. GET /api/v2/chat/messages/{id}.

ParametersJSON Schema

Name	Required	Description	Default
`id`	Yes	Message id.
`show_deleted`	No	Include the message even if soft-deleted. Default false.

stream_get_reactionsGet message reactions

Read-only

Inspect

List the reactions on a message. GET /api/v2/chat/messages/{id}/reactions.

ParametersJSON Schema

Name	Required	Description
`id`	Yes	Message id.
`limit`	No	Max reactions. Default 50.
`offset`	No	Pagination offset.

stream_get_repliesGet thread replies

Read-only

Inspect

Fetch the reply messages in a thread, given the parent message id. GET /api/v2/chat/messages/{parent_id}/replies.

ParametersJSON Schema

Name	Required	Description	Default
`limit`	No	Max replies (<=300). Default 25.
`parent_id`	Yes	Parent (thread-root) message id.

stream_get_unread_countsGet unread counts for a user

Read-only

Inspect

Fetch total and per-channel unread message/mention counts for one user. GET /api/v2/chat/unread.

ParametersJSON Schema

Name	Required	Description	Default
`user_id`	Yes	User id to fetch unread counts for.

stream_query_channelsQuery channels

Read-only

Inspect

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.

ParametersJSON Schema

Name	Required	Description
`sort`	No	Default [{"field":"last_message_at","direction":-1}].
`limit`	No	Max channels (<=30). Default 30.
`filter`	No	Stream filter_conditions object, e.g. {"type":"messaging"} or {"members":{"$in":["u1"]}}. Default {} (all channels the app can see).
`offset`	No	Pagination offset.
`message_limit`	No	Recent messages per channel to include. Default 25.

stream_query_membersQuery channel members

Read-only

Inspect

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.

ParametersJSON Schema

Name	Required	Description
`id`	Yes	Channel id.
`sort`	No	Sort spec, e.g. [{"field":"created_at","direction":1}].
`type`	Yes	Channel type, e.g. "messaging".
`limit`	No	Max members (<=100). Default 100.
`filter`	No	Member filter_conditions, e.g. {"user_id":{"$in":["u1","u2"]}}. Default {}.
`offset`	No	Pagination offset.

stream_query_threadsQuery threads

Read-only

Inspect

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.

ParametersJSON Schema

Name	Required	Description
`sort`	No	Sort spec for threads.
`limit`	No	Max threads (<=25). Default 10.
`user_id`	No	User id to scope thread participation/read-state to.
`reply_limit`	No	Replies to preview per thread. Default 3.

stream_query_usersQuery users

Read-only

Inspect

List/filter users in the app. e.g. filter {"role":{"$eq":"admin"}} or {"id":{"$in":["u1"]}}. GET /api/v2/users.

ParametersJSON Schema

Name	Required	Description
`sort`	No	Sort spec, e.g. [{"field":"created_at","direction":-1}].
`limit`	No	Max users (<=100). Default 100.
`filter`	No	User filter_conditions, e.g. {"role":{"$eq":"admin"}}. Default {} (all users).
`offset`	No	Pagination offset.

stream_search_messagesSearch messages

Read-only

Inspect

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.

ParametersJSON Schema

Name	Required	Description
`next`	No	Pagination cursor returned by a previous search.
`sort`	No	Sort spec for results.
`limit`	No	Max results (<=100). Default 20.
`query`	No	Full-text search string. Provide this OR message_filter.
`filter`	Yes	Channel filter_conditions, e.g. {"type":"messaging"} or {"members":{"$in":["u1"]}}.
`message_filter`	No	Message filter object, e.g. {"text":{"$q":"refund"}} or {"attachments":{"$exists":true}}.

stream_send_messageSend a message (WRITE — posts to Stream)

Destructive

Inspect

⚠️ 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.

ParametersJSON Schema

Name	Required	Description
`id`	Yes	Channel id.
`text`	Yes	Message text.
`type`	Yes	Channel type, e.g. "messaging".
`user_id`	Yes	Existing user id to send the message as.
`mentioned_users`	No	User ids to @mention.

stream_send_reactionSend a reaction (WRITE — posts to Stream)

Destructive

Inspect

⚠️ 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.

ParametersJSON Schema

Name	Required	Description
`id`	Yes	Message id to react to.
`user_id`	Yes	Existing user id to react as.
`reaction_type`	Yes	Reaction type, e.g. "like", "love", "haha".