Whatcanido — MCP Server for Service Businesses
Cross-product MCP server for CRM, LeadKit, ProjectKit, Bookio. 10 action types, MIT open spec.
| Endpoint | https://whatcanido.dev/api/mcp (streamable-http) |
|---|---|
| Registry version | 0.2.0 |
| Now | 10 tools · grade A (97) · pin ts_78b1b33a6d6890b597404e329953d3c8 · protocol 2025-06-18 |
| First / last listed | 2026-10-30 00:49 UTC / 2026-10-30 00:49 UTC |
| Grade over time | 2026-10-30: A (97), 10 tools |
Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.
Tools: find_providers get_provider_actions submit_action get_action_status discover_capabilities get_capability_spec plan_capabilities reverse_search_capabilities list_available_capabilities invoke_capability
find_providers | Search across whatcanido for providers (businesses, freelancers, SaaS tools) that can perform a given business-level action type. Returns a ranked list with provider_id, name, description, services, action_types. Call this FIRST, before any other tool. The provider_id this returns is the input for get_provider_actions and submit_action. When no providers match, BROADEN the search: drop `industry` params: action_type, query, city, country, industry, product, limit |
get_provider_actions | Return the action types a provider exposes and the canonical input schema for each (required fields, optional fields, types, descriptions). Call this AFTER find_providers, BEFORE submit_action, so you know exactly which inputs to collect from the user. params: provider_id*, action_type |
submit_action | Invoke an action on a specific provider. WRITE tool: creates leads/bookings/contacts/projects/activities/tickets on the underlying SaaS tenant. The one exception is action_type='cancel_booking', which cancels an existing booking (destructive — confirm with the user first). Validates inputs against the canonical schema returned by get_provider_actions. If you skip required fields, the response cont params: provider_id*, action_type*, inputs* |
get_action_status | Look up the current status of a previously submitted action by its request_id. Returns status (raw, e.g. 'new', 'sent', 'confirmed') + status_label (human, e.g. 'Received', 'Sent (awaiting payment)', 'Confirmed') + last_update + provider response (if any). Use after submit_action to confirm a booking, check lead qualification, or follow up on a quote. params: request_id* |
discover_capabilities | Search the whatcanido capability registry by free-text intent. Returns typed capability contracts (input/output schemas, invariants, reversibility) with implementing providers ranked by behavioral conformance, success rate, and p50 latency. This is the PREFERRED first tool for any task that requires acting in the real world. Each match includes 'why_relevant' (LLM-generated reasoning), 'spec_url' params: intent*, context, limit |
get_capability_spec | Return the full canonical contract for a capability: JSON Schemas for input and output, declared invariants, semantics, reversibility, side effects, auth model, when-to-use guidance. Plus the list of providers that implement it with current reputation snapshot. Use this AFTER `discover_capabilities` and BEFORE `invoke_capability` so you know exactly which inputs to collect and which provider to in params: capability_id* |
plan_capabilities | Given a user intent, return a typed plan: an ordered list of capability calls that together accomplish the goal, with the highest-reputation provider per step. The plan respects the capability registry's prerequisite graph — for example a plan that includes `booking.create_booking` automatically prepends `booking.check_availability`. Use this when the user's request spans more than one verb (e.g. params: intent*, context, limit |
reverse_search_capabilities | Given a JSON payload (something you found in user context, a webhook body, an export, a clipboard paste), return the capabilities whose input or output schema overlaps with the payload's shape. Use this when you don't have a verb-style intent but you do have data and want to ask 'what could I do with this?'. Returns matches ranked by structural overlap with `direction: 'input' | 'output' | 'both'` params: payload* |
list_available_capabilities | Return a compact roster of every capability with at least one enabled provider, grouped by category, with the best current conformance per capability. Use this as a self-introspection step: call once at the start of a task to know what is and isn't available, before deciding whether to attempt or to tell the user 'this isn't possible here'. params: none |
invoke_capability | Execute a capability call against a chosen provider with typed inputs. WRITE tool when the capability's category ends in '.write' (creates state, sends notifications, charges money, etc.) — confirm with the user before calling for any non-reversible capability. Read capabilities (category ending '.read') are safe to call without confirmation. Validates inputs against the capability's JSON Schema. params: capability_id*, provider_id*, inputs*, agent_vendor |
Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.