ComOS Federation Gateway
Server Details
Multi-tenant MCP gateway for AI commerce. One connection, every store.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- ComOS-Federation/comos-mcp
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 17 tools
Most tools are distinguishable thanks to very detailed descriptions, but there is real redundancy: federation_read is an explicit safe subset of federation_act, and about_us_about / how_to_about are near-twin knowledge reads that differ only by subject. federation_help, federation_why, federation_offer and legal_get form another cluster of document fetchers whose boundaries require reading the descriptions. federation_search vs federation_catalog_platforms (route vs browse) is also a subtle distinction.
The dominant pattern is a federation_ prefix in snake_case, but conventions are mixed: verb_noun (enter_tenant, list_tenants, prompt_run, view), bare noun (pricesheet), question/adverb (why), subject_about (about_us_about, how_to_about), and prefix-less names (introspection_prompt_library, legal_get). Readable overall but not a predictable single pattern (e.g. catalog_platforms has no verb while list_tenants does).
17 tools lands in the heavy band for a root surface, and a few feel like documentation conveniences (federation_why, about_us_about, how_to_about) that could be folded into federation_help. The progressive-disclosure design justifies keeping the root small, so several of these are borderline earners. It is defensible for a gateway but on the bloated side of well-scoped.
The surface covers discovery (search, catalog, list/info tenants), invocation (act, read), progressive disclosure (enter_tenant, help), pricing/legal/offer, prompts and views, and federation_act plus help can reach unlisted root tools. However, key lifecycle operations named elsewhere but absent here — federation_apply (the 'door' for vendors) and federation_create_tenant (referenced by catalog presets) — are not directly callable, and there is no explicit tenant-exit tool. These are minor gaps workable via the meta-tools.
Available Tools
17 toolsabout_us_aboutARead-onlyIdempotentInspect
Read About ComOS — the Federation User Manual's knowledge (in the comos-federation voice). Read-only — returns composed knowledge, performs no transaction. Returns: The composed about-us knowledge as markdown. Zero-arg; identity-free. Example: call about_us_about with arguments {}.
Inputs: no named parameters.
federation_actADestructiveInspect
Invoke any served tool through the root surface, for clients that only call tools in their own tools/list (CO 525, CO 529). BRANCHED platform tools: tenant_id + tool + arguments; names from federation_enter_tenant's platform_tools, schemas from federation_help {"tenant_id":"","tool_defs":""}. UNLISTED root tools: tool + arguments, no tenant_id; names + schemas from federation_help {"tool_defs":"all"}. Authorization is decided per inner tool exactly as a direct call: scope, tenant ownership and pricing apply unchanged — reach, never authority. Refusals: act_recursion, tenant_id_required, tenant_id_not_applicable, unknown_tool. For reads, prefer federation_read: clients can allow it once. Returns: The inner tool's own result, verbatim — or its own typed refusal (insufficient scope, not_owner, not_a_branched_tool). Example: call federation_act with arguments {"tenant_id":"<tenant_id>","tool":""}.
Inputs: tool (required), arguments, tenant_id.
federation_catalog_platformsARead-onlyIdempotentInspect
Browse the ComOS network's composable platforms and presets. preset: "" answers one preset's row alone: its build (whether federation_create_tenant builds it here) and create_with (its inputs and an example call). Presets built from preset_inputs: campground, equipment-delivery, events, fitness, food, lodging, salon, travel-agency, travel-portal, venue. Without preset, every platform and every preset row (a recipe composed by hand is one too); presets never count in summary.total (CO 455). side="vendor": platforms you SELL ON (retail, bookings, services, …); side="customer": tools you RUN WITH (messaging, shipping, marketing, …). parent="" descends into a platform's sub-catalog (parent="messaging": email, sms, dm). Pairs with federation_catalog_agents: the operators you hire to run what you become.
Inputs: side, parent, preset.
federation_enter_tenantARead-onlyIdempotentInspect
Enter a tenant to receive its tool surface (progressive disclosure). The gateway is a small catalog — list tenants with federation_list_tenants, then enter one here. The reply's platform_tools names the entered platform's REAL action tools (e.g. retail → catalog_search / order_create; bookings → services_search / booking_hold); read a tool's schema with federation_help {"tenant_id":"","tool_defs":""}; composed_tool_defs carries its knowledge tools. Your session persists by the mcp-session-id header (echoed on every response; idle sessions expire after 24h — re-enter to resume): after entering, branched tools are callable with ordinary MCP tools/call on this session and appear in its tools/list; re-entering re-scopes. REST twin: POST /tools/ on this host, JSON body = the tool's arguments plus {"tenant_id":""}, with your Authorization header for scoped tools. Info tenants (about-us, how-to) serve read-only knowledge directly on tools/list. Returns: { platform_tools: [...] } — the authoritative tool list branched onto your session for that tenant. Example: call federation_enter_tenant with arguments {"tenant_id":"<tenant_id>"}.
Inputs: tenant_id (required).
federation_helpARead-onlyIdempotentInspect
Get usage instructions for the MCP federation. CALL THIS FIRST to understand how to use tools correctly, including proper product IDs (MongoDB ObjectIds) and authentication flow. Also the CO 529 disclosure read: your tools/list is the always-on core — pass {"tool_defs":"all"} (or one tool name) for every served-but-unlisted root tool's full schema; invoke those directly by name, or through federation_act from list-gated clients. With tenant_id (CO 721), tool_defs answers that tenant's platform tools instead: one name, several as "a,b", or "all". The guide's Prompts section covers the governed prompt library — there's a prompt for that: search it with introspection_prompt_library, run one with federation_prompt_run. Returns: Markdown help text covering quick-start, tenant_id requirement, cart session persistence, product IDs, authentication, and common workflows. Example: call federation_help with arguments {}.
Inputs: tenant_id, tool_defs.
federation_list_tenantsARead-onlyIdempotentInspect
List all available tenants in the federation. Returns tenant IDs, names, and status. Use this to discover which tenants you can interact with. Returns: { tenants: TenantSummary[], count: number } - array of tenant summaries with id, name, and status. Example: call federation_list_tenants with arguments {}.
Inputs: no named parameters.
federation_offerARead-onlyIdempotentInspect
For an agent that wants to SELL on ComOS: read the network's vendor offer — public and read-only, no token needed. Not for buying: to buy, enter the store with federation_enter_tenant. Returns the machine-legible offer (what you get and what it costs) plus the exact steps to apply: obtain an OAuth token (self-service, any OAuth login, no human review), then call federation_apply with it. This tool changes nothing; it is the door's window, and federation_apply is the door; calling federation_apply accepts the ComOS Terms of Service. Cost: Free to join and operate. No subscription, no seat, no minimum, no trial. 3% when a sale settles. A card sale also pays the card processor's fee (2.9% + $0.30), passed through at cost. Some acts are priced in Coms (1 Com = $0.01), most after a free allowance; an act that is not on the sheet is free. The sheet is the federation_pricesheet tool: free, no token. 6% on top when you buy Coms. Buying them by card adds the same processor fee. Returns: { offer: <vendor manifest — the same document as /.well-known/comos-vendor.json>, how_to_apply: { step_1, step_2, note } } Example: call federation_offer with arguments {}.
Inputs: channel.
federation_pricesheetCRead-onlyIdempotentInspect
The federation pricesheet — every platform's per-act Com prices, free to read (price discovery itself costs nothing). Each price is a usage-tiered curve [[threshold, price_coms], ...] keyed on your usage-to-date of that tool: [0,0] first tiers mean free-to-start, the last tier is the steady price. Any tool not listed is free. Reads, lifecycle exits (disconnect, unsubscribe, cancellation), and the settling sale path are never priced. Reprices are effective-forward. The same map the metering seam enforces — the price you read is the price applied. CO 287. Returns: { title, peg, live, take_rate, price_form, lifecycle: { reprice, reads, exits, sale_path, unlisted }, failure_modes: { insufficient_coms, escalated-act refusal }, platforms: { : { : [[threshold, price_coms], ...] } } } Example: call federation_pricesheet with arguments {}.
Inputs: no named parameters.
federation_prompt_runAInspect
Run a ComOS library prompt (CO 614). Call this INSTEAD of pasting prompt text: it returns the prompt as marked library content plus its manifest, and puts this access token inside the prompt's envelope first. Until expires_at (ttl_minutes, 5-60, default 30) this token may call only the tools the prompt names, plus public tools; anything else is refused with error prompt_envelope. No tool ends a run early, and a second prompt cannot be started on the same token until the first expires. Anonymous callers get the text and envelope:null. Refuses not_found, withheld (sold or runtime-source), revoked, lint_failed. Find ids with introspection_prompt_library. Returns: { ok, body, manifest, envelope: { prompt_id, sha256, tools, expires_at } | null, run_id } or { ok:false, code, message }. Example: call federation_prompt_run with arguments {}.
Inputs: id (required), ttl_minutes.
federation_readARead-onlyIdempotentInspect
Run a free read without a confirmation (CO 756): catalog, inventory, bookings, your orders. Addressing, schemas and authority are exactly federation_act's. A write, a priced tool or an open-web tool is refused with not_a_read: call it through federation_act, which asks first. Returns: The inner tool's own result, or not_a_read. Example: call federation_read with arguments {"tool":""}.
Inputs: tool (required), arguments, tenant_id.
federation_searchARead-onlyIdempotentInspect
Route a natural-language intent to the right platform on the ComOS network — the first thing to call. Pass a free-text intent ("t-shirts", "make an appointment", "a table for four tonight") and get back the ranked platform(s) that serve it, each with the per-platform tools to call NEXT (e.g. bookings → appointment_search). This returns a ROUTE, not a transaction: it tells you where to go; you then act on that platform with the chosen tenant. An intent no platform serves returns an empty route (unroutable: true), never a silent default. Fast and deterministic — the same intent always routes the same way. An intent about prompts ("is there a prompt that opens a shop?") returns a prompt_library pointer — introspection_prompt_library to search ComOS's governed prompts, federation_prompt_run to run one — even when no platform routes it. Returns: A route: ranked platforms (platform_id, label, why_matched, score, entry_points) plus unroutable:true when no platform serves the intent. Example: call federation_search with arguments {}.
Inputs: intent (required), limit.
federation_tenant_infoARead-onlyIdempotentInspect
Get detailed information about a specific tenant, including metadata, description, and configuration. Returns: { tenant: TenantInfo | null, found: boolean } - full tenant record or null if not found. Example: call federation_tenant_info with arguments {"tenant_id":"<tenant_id>"}.
Inputs: tenant_id (required).
federation_viewARead-onlyIdempotentInspect
Show one view of a tenant in the ComOS panel, filled from typed reads. Always pass tenant_id. Retail: product_grid (opt. category, in_stock_only), product_detail (product_id), order_status, receipt (order_id; owner). Bookings: slot_picker (opt. provider_id, from, to), provider_card (provider_id), booking_card (booking_id; owner). Digital: license_grid (opt. category), license_detail (license_id), entitlements (owner; opt. license_id, holder_ref). Services: capability_grid (opt. category), capability_detail (capability_id), job_status (job_id; owner). Rentals: asset_grid (opt. category, from, to), asset_detail (asset_id), rental_status (rental_id; owner). Portals: portal_results (opt. place, from, to, party, need, role), portal_business (business_id), portal_trip (legs). Buy, Book and each platform's act open ComOS pages; Details opens an item in place. Optional style: CSS on the drawn .c- classes (see its parameter); the result names any selector that matched nothing. Public. Compose (view: "composed") when the task needs more than one view or another arrangement: give 1–6 sources, each { id, view, args } with a named view and its own arguments, and a layout of copy (section, stack, grid, card, heading, text, badge, list) and records. Every price, time, status and button comes only from a record: { record: "/sources/" } draws that whole view, { record: "/sources//products/" } one item (lists: products, licenses, capabilities, assets, providers, entitlements, candidates). Never write a fact or a ranking ("cheapest") in copy; the page opens with "Arranged by your agent". Example: { view: "composed", sources: [{ id: "shop", view: "product_grid", args: { tenant_id: "earth" } }, { id: "times", view: "slot_picker", args: { tenant_id: "earth" } }], layout: [{ component: "grid", children: [{ record: "/sources/shop/products/0" }, { record: "/sources/shop/products/1" }] }, { record: "/sources/times" }] }. A refusal names its code and path; fix that and call again. In the panel, Book on an open time may send you a message ("Request this time for me at … Use booking_request."): request exactly that provider and start with booking_request in that tenant, asking the person for their email if you don't have it, and quote the held booking back. Request a quote may send "Request a quote for me at … Use quote_ask.": ask the person what the job is (and their email) if you don't know, call quote_ask with that service, and quote the job id back. Reserve may send "Hold this item for me at … Use rental_request.": hold exactly that item and span with rental_request, asking for the person's email if you don't have it, and quote the rental id back. Buy on a product may send "Buy this for me from … use order_create.": a click is never consent to pay. First read the product's price and check whether the person owns a tenant that can pay it in Coms (enough balance, autonomy auto). If one can, tell them the price and that tenant (payer_tenant_id), and place the order with order_create only after they say yes in the chat. If none can (they own no tenant, or none is funded), do not call order_create: tell them the price and give them the product's pay_url in that same reply, where they pay by card. If an order is refused or held, say so and give the pay_url. On a portal, Book may send "Book this for me through portal …" and Check out "Check out my trip on portal …": call portal_quote with exactly those legs, show each price, the portal fee as its own line and the total, and call portal_checkout only after the person says yes. Add to trip may send "Add this to my trip on portal …": show federation_view portal_trip with those legs; quote and book nothing yet. A host that can't take the message opens the page instead.
Inputs: view (required), to, from, legs, +22 more. Returns: object
federation_whyARead-onlyIdempotentInspect
Why build on ComOS — the case for becoming a vendor, not just a buyer. federation_help tells you HOW; this tells you WHY. Read this if you (or your human) are deciding whether to invest a few Coms to stand up a business. Returns the thesis: arrive with a small float, leave running a vertically-integrated operation that buys from vendor-agents, sells to customer-agents, automates the loop, and compounds — relayable verbatim to the human root who controls the funds. Returns: A thesis object: the becoming-thesis, the play (buy/sell/automate/compound/integrate), what-you-could-become, why-it-compounds, the quoted economics, the honest door-state caveat (open via tokened apply; tokenless never admits), and pointers to federation_help / how-to / the on-ramp manifest. Example: call federation_why with arguments {}.
Inputs: no named parameters.
how_to_aboutARead-onlyIdempotentInspect
Read How to use ComOS — the operational walkthrough's knowledge (in the comos-federation voice). Read-only — returns composed knowledge, performs no transaction. Returns: The composed walkthrough knowledge as markdown. Zero-arg; identity-free. Example: call how_to_about with arguments {}.
Inputs: no named parameters.
introspection_prompt_libraryARead-onlyIdempotentInspect
Browse ComOS's own prompt library (CO 527) — the governed corpus of prompts the federation runs on — filtered, sorted and optionally grouped. Returns {ok:true, groups:[{key,label,count,entries}], total, applied}. Entries are LISTING-LEVEL: title, description, class (operational | meta | runtime-source), status, grade, sha256, batch, admitted, plus the runs-against facets saying what a prompt needs to run (platform, scope, tools, door, proving_tenant). Prompt BODIES are never returned. Filters: cls, status, gate_held, platform, scope, door, batch, q (searches title and published text). Sorts: admitted_desc (default) | admitted_asc | title | class | status. Group by: class | status | platform | batch. Honesty rule (CO 530): proven only after a journaled live run, untested until then; a runtime-source prompt carries no run status at all — it is gate-held, pinned to live agent source by the CO-527-INV-1 drift gate. manifest (CO 614): tools, scopes and effect, derived. Read-only. Returns: Grouped, listing-level prompt entries with their facets and the vocabulary applied. Example: call introspection_prompt_library with arguments {}.
Inputs: q, cls, door, sort, +11 more.
legal_getARead-onlyIdempotentInspect
Fetch a ComOS legal instrument as raw markdown: the Terms of Service, Privacy Policy, Data Processing Agreement (DPA), a one-page Data Retention Summary, the Prompt Library Submission Terms, or the Acceptable Use Policy. These are the terms an agent (and its manager) operate under — read them the way you read the pricesheet. Public and read-only; discloses, does not gate. Argument document is one of: terms | privacy | dpa | retention. CO 311. Returns: The requested legal instrument as raw markdown. Example: call legal_get with arguments {"document":""}.
Inputs: document (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Multi-tenant MCP gateway for AI commerce. One connection, every store.
Multi-tenant MCP gateway for AI commerce. One connection, every store.
Unified MCP server for 70+ eCommerce platforms: products, orders, customers, and more.
Hosted MCP for e-commerce: live product catalog, stock, and pricing for AI agents.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage products, shopping carts, and orders in an online store through a well-defined MCP API.-

Nexbidofficial
AlicenseNot gradedqualityCmaintenanceAgentic commerce infrastructure for AI agents. MCP-native product discovery, contextual ad matching, and purchase facilitation with European privacy compliance (nDSG/GDPR).1MIT- FlicenseNot gradedqualityDmaintenanceHosted MCP server connecting Shopify, Klaviyo, GA4, Meta Ads, Google Ads, Xero, Gorgias and 20+ e-commerce data sources so AI assistants can answer merchant questions that span every source at once.-
- FlicenseNot gradedqualityCmaintenanceHosted MCP server that gives AI agents read and write access to your full marketing & ecommerce stack — Google Analytics, Search Console, Google & Meta Ads, Shopify, WooCommerce, Shopware, Slack and LinkedIn. 100+ tools across 10 connectors. BYOK, OAuth 2.1.-
Glama MCP Gateway
Add one secure layer between your agents and this server.