Run your business from an AI agent

FASS MCP is a Model Context Protocol server. Connect it to Claude — or any MCP client — and an AI agent can operate your FASS workspace end‑to‑end: stand up an AI receptionist, give it a phone number, teach it, book appointments, and pull matched federal solicitations. No dashboard, no API keys to paste.

What can I actually do?

You never call these tools yourself. You tell Claude what you want in plain English, and it chains the right tools together. For example, in a single prompt:

Claude will automatically:

• Create your business
• Configure the AI receptionist from your website
• Purchase a phone number (with your approval)
• Import your hours, services, and FAQs
• Sync appointments to your connected Google Calendar
• Begin answering calls and booking clients

Overview

The FASS MCP server exposes your workspace as a set of tools an AI agent can call on your behalf. It speaks JSON‑RPC over HTTP at a single endpoint and authenticates with OAuth 2.1, so a client like Claude can discover it, sign you in, and start working — no key management.

Every tool is scoped to the businesses on your own account, and write actions (texting a lead, buying a number, booking) default to approval‑required in the client, so nothing happens without your say‑so.

Quickstart

In Claude, add FASS as a custom connector. The whole handshake takes about 30 seconds.

Authentication

FASS MCP is a full OAuth 2.1 authorization server. Clients that support MCP OAuth (like Claude) do the entire flow automatically:

• Discovery — the client reads /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server.
• Dynamic client registration — the client registers itself (RFC 7591); you never create credentials by hand.
• PKCE authorize + token — you approve access through your normal FASS login; the client receives a scoped token.

If a request arrives without a valid token, the endpoint returns 401 with a WWW-Authenticate challenge that points the client at discovery — which is what triggers the sign‑in prompt.

# A tool call, once authenticated
POST /api/v1/voice/mcp
Authorization: Bearer <token>
{
  "jsonrpc": "2.0", "id": 1,
  "method": "tools/call",
  "params": {
    "name": "create_business",
    "arguments": { "name": "Parenting Law", "timezone": "America/New_York" }
  }
}

Tools reference

19 tools, grouped by what they do. Optional parameters are marked ?. When you have one business, business_id can be omitted and FASS uses it automatically.

Provisioning

Knowledge

Booking

Flow & govcon

Read & act

Use cases

Because the tools compose, one instruction can chain several. A few things you can just ask for:

• Onboard from chat — “Spin up a receptionist for my law firm from our website, give it a 443 number, and teach it our hours.” (create_business → set_agent → provision_number → set_faq)
• Convert a caller — “Book the caller Thursday at 2pm and add it to my calendar.” (get_availability → book_appointment)
• Work the govcon pipeline — “Email me the federal solicitations matched to my business.” (list_solicitations → email_solicitation_digest)
• Follow up — “Text the warm lead our booking link and log a follow‑up to call them tomorrow.” (send_sms → create_followup)

Security & tenancy

• Scoped to you. Every tool resolves against the businesses on your own account. A business id that isn't yours returns nothing.
• Approval by default. Write tools (send_sms, provision_number, book_appointment, email_solicitation_digest, …) default to approval‑required in the client.
• Digest goes only to you. email_solicitation_digest can only send to your own account email — never an address supplied in a prompt.
• Hard guards. Double‑booking is prevented by a database constraint, not a best‑effort check.

Pricing

Get started →  ·  See the FASS Suite bundle →