arena-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| arena_searchB | Search Are.na (visual references: channels, image blocks, users). Returns compact objects with an image URL and an are.na link. Works without a token. |
| arena_channelB | Channel metadata (reference collections) by slug or id, including the description. |
| arena_channel_contentsA | Blocks inside a channel (the references themselves, with image URLs). Paginated. Use after arena_search to expand a collection you found. |
| arena_blockA | Details of a single block (image/link/text) by id, plus the channels it was added to. |
| arena_user_channelsB | List a specific author's channels by slug or id — to dig through their collections. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct resource: search results, channel metadata, channel contents, individual blocks, and a user's channels. There is no meaningful overlap, and the intended workflow (search -> channel -> contents -> block) is clear.
All tool names follow the same arena_ + noun pattern with snake_case and the server prefix applied uniformly. Even though search is more action-like, the overall naming is predictable and easy to extrapolate.
Five tools is a well-scoped set for a read-only Are.na browsing server. Each tool covers a distinct primary object or action, and the count is neither bloated nor too thin for the apparent purpose.
The set covers the core read-only workflows: search, inspect channels, page through contents, view block details, and list a user's channels. Minor gaps exist, such as direct user profile metadata or broader discovery feeds, but they do not break the main usage flow.