affinity-mcp-bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AFFINITY_MCP_SSE_URL | No | URL for Affinity's MCP SSE server | http://localhost:6767/sse |
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| affinity_statusA | Check whether the bridge can connect to Affinity by Canva's local MCP server. |
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 1 tool
Only one tool exists, so there is no possible confusion between tools. The purpose of the single tool is clear.
With a single tool, naming is trivially consistent. The name follows a descriptive verb_noun pattern.
A single health-check tool is insufficient for a server named 'affinity-mcp-bridge', which implies a range of operations. The tool count is far too low for the implied scope.
The tool surface is severely incomplete; it only provides a status check and lacks any CRUD or lifecycle operations for Affinity's resources, making it nearly useless for actual tasks.