stream
Server Details
Query channels, search messages, and read threads, users and reactions in your Stream Chat app.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
13 toolsstream_get_appGet app settingsRead-onlyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
stream_get_channelGet channel state + recent messagesRead-onlyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| 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 messageRead-onlyInspect
Fetch a single message by its id. GET /api/v2/chat/messages/{id}.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Message id. | |
| show_deleted | No | Include the message even if soft-deleted. Default false. |
stream_get_reactionsGet message reactionsRead-onlyInspect
List the reactions on a message. GET /api/v2/chat/messages/{id}/reactions.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Message id. | |
| limit | No | Max reactions. Default 50. | |
| offset | No | Pagination offset. |
stream_get_repliesGet thread repliesRead-onlyInspect
Fetch the reply messages in a thread, given the parent message id. GET /api/v2/chat/messages/{parent_id}/replies.
| 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 userRead-onlyInspect
Fetch total and per-channel unread message/mention counts for one user. GET /api/v2/chat/unread.
| Name | Required | Description | Default |
|---|---|---|---|
| user_id | Yes | User id to fetch unread counts for. |
stream_query_channelsQuery channelsRead-onlyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| 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 membersRead-onlyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| 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 threadsRead-onlyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| 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 usersRead-onlyInspect
List/filter users in the app. e.g. filter {"role":{"$eq":"admin"}} or {"id":{"$in":["u1"]}}. GET /api/v2/users.
| Name | Required | Description | Default |
|---|---|---|---|
| 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 messagesRead-onlyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| 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)DestructiveInspect
⚠️ 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.
| Name | Required | Description | Default |
|---|---|---|---|
| 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)DestructiveInspect
⚠️ 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.
| Name | Required | Description | Default |
|---|---|---|---|
| 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". |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!