A
licenseNot graded
qualityD
maintenanceEnables AI assistants to programmatically create, manage, and orchestrate n8n workflows through a standardized MCP interface.
MIT
Workflow
Server Details
Create, browse, remix, collaborate on, and run durable AI workflow nodes from MCP hosts.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- Jonnyton/TinyAssets
- GitHub Stars
- 1
- Server Listing
- TinyAssets
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
- Changed
write_graph5 fields changed- added
Input schema / properties / directed_daemon_idAdded value: +{ + "default": "", + "description": "Optional requester-owned daemon target.", + "type": "string" +} - added
Input schema / properties / directed_daemon_instructionAdded value: +{ + "default": "", + "description": "Optional direction for that daemon.", + "type": "string" +} - added
Input schema / properties / idempotency_keyAdded value: +{ + "default": "", + "description": "Required 16-128 character request idempotency key.", + "type": "string" +} - added
Input schema / properties / pickup_incentiveAdded value: +{ + "default": "", + "description": "Optional requester pickup incentive terms.", + "type": "string" +} - added
Input schema / properties / priority_weightAdded value: +{ + "anyOf": [ + { + "type": "integer" + }, + { + "type": "number" + } + ], + "default": 0, + "description": "Requested numeric priority in inclusive range 0-100." +}
1 tool update
- Changed
write_graph1 field changed- changed
Input schema / properties / request_type / descriptionPrevious value: -"Workflow request type."New value: +"TinyAssets request type."
10 tool updates
- Added
read_graph - Added
read_page - Removed
read.graph - Removed
read.page - Added
run_graph - Removed
run.graph - Added
write_graph - Added
write_page - Removed
write.graph - Removed
write.page
1 tool update
- Changed
read.page1 field changed- changed
Input schema / properties / changed_since / descriptionPrevious value: -"Optional ISO timestamp for feed freshness filtering.\nWith an empty page/query/category, returns pages changed after this\ntimestamp."New value: +"Optional ISO timestamp for feed freshness filtering. With an empty page/query/category, returns pages changed after this timestamp."
2 tool updates
- Changed
read.page1 field changed- added
Input schema / properties / universe_idAdded value: +{ + "default": "", + "description": "Optional target universe page substrate.", + "type": "string" +}
- Changed
write.page1 field changed- added
Input schema / properties / universe_idAdded value: +{ + "default": "", + "description": "Optional target universe page substrate.", + "type": "string" +}
1 tool update
- Changed
read.page1 field changed- changed
Input schema / properties / changed_since / descriptionPrevious value: -"Optional ISO timestamp for feed freshness filtering."New value: +"Optional ISO timestamp for feed freshness filtering.\nWith an empty page/query/category, returns pages changed after this\ntimestamp."
16 tool updates
- Removed
get_workflow_goal - Removed
get_workflow_status - Removed
inspect_workflow_universe - Removed
list_workflow_goals - Removed
list_workflow_runs - Removed
list_workflow_universes - Removed
propose_workflow_goal - Removed
read_workflow_wiki_page - Added
read.graph - Added
read.page - Added
run.graph - Removed
search_workflow_goals - Removed
search_workflow_wiki - Removed
submit_workflow_request - Added
write.graph - Added
write.page
1 tool update
- Changed
read_workflow_wiki_page3 fields changed- added
Input schema / properties / changed_sinceAdded value: +{ + "default": "", + "description": "Optional ISO timestamp for feed freshness filtering.", + "type": "string" +} - added
Input schema / properties / max_resultsAdded value: +{ + "default": 10, + "description": "Maximum ambient feed items to return.", + "type": "integer" +} - added
Input schema / properties / queryAdded value: +{ + "default": "", + "description": "Optional topic terms for the ambient relevance feed.", + "type": "string" +}
11 tool updates
- Changed
get_workflow_goal1 field changed- changed
Output schema / (root)Previous value: -{ - "properties": { - "result": { - "type": "string" - } - }, - "required": [ - "result" - ], - "type": "object", - "x-fastmcp-wrap-result": true -}New value: +null
- Changed
get_workflow_status1 field changed- changed
Output schema / (root)Previous value: -{ - "properties": { - "result": { - "type": "string" - } - }, - "required": [ - "result" - ], - "type": "object", - "x-fastmcp-wrap-result": true -}New value: +null
- Changed
inspect_workflow_universe1 field changed- changed
Output schema / (root)Previous value: -{ - "properties": { - "result": { - "type": "string" - } - }, - "required": [ - "result" - ], - "type": "object", - "x-fastmcp-wrap-result": true -}New value: +null
- Changed
list_workflow_goals1 field changed- changed
Output schema / (root)Previous value: -{ - "properties": { - "result": { - "type": "string" - } - }, - "required": [ - "result" - ], - "type": "object", - "x-fastmcp-wrap-result": true -}New value: +null
- Changed
list_workflow_runs1 field changed- changed
Output schema / (root)Previous value: -{ - "properties": { - "result": { - "type": "string" - } - }, - "required": [ - "result" - ], - "type": "object", - "x-fastmcp-wrap-result": true -}New value: +null
- Changed
list_workflow_universes1 field changed- changed
Output schema / (root)Previous value: -{ - "properties": { - "result": { - "type": "string" - } - }, - "required": [ - "result" - ], - "type": "object", - "x-fastmcp-wrap-result": true -}New value: +null
- Changed
propose_workflow_goal1 field changed- changed
Output schema / (root)Previous value: -{ - "properties": { - "result": { - "type": "string" - } - }, - "required": [ - "result" - ], - "type": "object", - "x-fastmcp-wrap-result": true -}New value: +null
- Changed
read_workflow_wiki_page1 field changed- changed
Output schema / (root)Previous value: -{ - "properties": { - "result": { - "type": "string" - } - }, - "required": [ - "result" - ], - "type": "object", - "x-fastmcp-wrap-result": true -}New value: +null
- Changed
search_workflow_goals1 field changed- changed
Output schema / (root)Previous value: -{ - "properties": { - "result": { - "type": "string" - } - }, - "required": [ - "result" - ], - "type": "object", - "x-fastmcp-wrap-result": true -}New value: +null
- Changed
search_workflow_wiki1 field changed- changed
Output schema / (root)Previous value: -{ - "properties": { - "result": { - "type": "string" - } - }, - "required": [ - "result" - ], - "type": "object", - "x-fastmcp-wrap-result": true -}New value: +null
- Changed
submit_workflow_request1 field changed- changed
Output schema / (root)Previous value: -{ - "properties": { - "result": { - "type": "string" - } - }, - "required": [ - "result" - ], - "type": "object", - "x-fastmcp-wrap-result": true -}New value: +null
11 tool updates
- First observed
get_workflow_goal - First observed
get_workflow_status - First observed
inspect_workflow_universe - First observed
list_workflow_goals - First observed
list_workflow_runs - First observed
list_workflow_universes - First observed
propose_workflow_goal - First observed
read_workflow_wiki_page - First observed
search_workflow_goals - First observed
search_workflow_wiki - First observed
submit_workflow_request
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
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
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
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!
Related MCP Connectors
Social network for AI builders: agents post, reply, search, remix and compose in styles over MCP.
161Discover, preview, estimate, run, and retrieve reusable AI workflows.
Give any MCP-compatible AI assistant a builder for live, hosted web tools and workflows.
Automate 1,000+ services from any MCP-compatible AI agent: build Applets, run actions and queries.
Related MCP Servers
- FlicenseCqualityAmaintenanceSelf-hosted, source-available AI workflow automation platform. Build multi-agent, RAG, and tool-using pipelines on a visual canvas and publish any workflow as an MCP server (stdio/SSE/Streamable HTTP). Also an MCP client via the agent node.21,090-
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to visually build and run AI generation pipelines on a canvas by adding, wiring, and executing nodes via MCP tools.Apache 2.0
FlowDot MCP Serverofficial
AlicenseNot gradedqualityAmaintenanceConnect any MCP-compatible AI client to the entire FlowDot platform, enabling management of workflows, recipes, custom nodes, apps, knowledge bases, agent toolkits, and community features.91-
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.5/5.0
Disambiguation5/5
Each tool targets a distinct action (read/write/run) on a distinct resource (graph/page), with no overlap in purpose.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern (e.g., read_graph, write_page), making the naming predictable and clear.
Tool Count5/5
With 5 tools covering core graph and page operations, the count is well-scoped for the domain.
Completeness4/5
The tool surface covers read, write, and run for graphs, and read/write for pages. Missing delete and list operations, but the set is functional for basic workflows.