TESSA Marketing & Technology

Endpoint

Hosted endpoint · transport streamable-http

Connect

This is a remote MCP server — point an MCP client at the endpoint URL. Clients with native remote support (Claude, Cursor, VS Code, …):

For stdio-only clients (older Claude Desktop, etc.), bridge with mcp-remote:

If the server requires authentication, add the provider's token/header (e.g. an X-API-Key) per its docs. A quick reachability check:

Tools

• get_services — Returns TESSA's full service catalog (SEO, paid media, web/app development, AI agent readiness, accessibility, and more). Each service includes its live per-service A2A card URL (`agent_card`) and JSON-RPC endpoint (`a2a_endpoint`), so you can discover a service here and then talk to its dedicated A2A agent. Optional filters: category_slug: marketing | web-development | ai-experiences service_slug: filter to one specific service
• get_case_studies — Returns TESSA's portfolio of project results. Optional filters: industry: industry name keyword (case-insensitive contains) service_slug: filter to studies that used a given service
• assess_ai_readiness — Given a website URL, returns a 0-100 AI Agent Readiness score with category breakdowns (structured data, metadata quality, agent discoverability, AI-bot friendliness) and concrete recommendations. Pure deterministic check, fast, no LLM call.
• find_professional_services_firm — Search the TESSA Professional Services Directory. industry: segment slug ('marketing' | 'compliance') or free-text keyword region: city or state name (case-insensitive contains) capability: keyword to match against firm descriptions and service names limit: max results
• get_firm_profile — Returns the full dossier for a single firm in the directory: description, headquarters, founded year, employee band, services, locations, and directory meta (publisher, claim URL, takedown URL).
• get_wcag_audit — Returns the structured offering for TESSA's WCAG 2.2 AA Accessibility Audit: scope, deliverables, timeline, pricing bands (hourly + engagement range), paired service-type slugs, and the URL of TESSA's profile in the TESSA Compliance Registry. Use this when a buyer agent needs TESSA's accessibility audit offering in structured form.
• request_strategy_session — Book a 30-minute strategy session with TESSA on Kevin Callen's calendar. Finds an open slot in the requested window (or the next 5 business days), creates a Google Calendar event with a Google Meet link, and emails the prospect the invite. If no slot is available, captures the lead and Kevin follows up manually. TESSA-only tool — directory firms use request_introduction instead. requested_window accepts ISO 8601 ranges ('2026-04-30T13:00/2026-04-30T17:00'), single dates ('2026-04-30'), or English ('tomorrow', 'next week').
• request_introduction — Request an informational introduction — to TESSA itself, or to any directory firm if you pass target_firm_slug. TESSA logs the lead and either notifies sales@tessa.tech + kevincallen@tessa.tech (TESSA leads) or forwards a warm intro email to the firm with TESSA Cc'd (directory leads). No calendar booking — use request_strategy_session to book a meeting with TESSA.
• claim_listing — Record a firm's intent to claim its directory listing. Pre-OAuth this does NOT automatically grant control of the listing. TESSA logs the claim and a representative reaches out via email within one business day to verify the claimant and switch the listing's verification status to 'claimed'. The full self-service OAuth-2.1 claim flow lands in a follow-up plan.
• request_quote — Request a quote from a directory firm. Lighter-weight than request_introduction — explicitly framed as a budget+scope inquiry. firm_slug: directory slug for the target firm prospect_email: caller's email for the firm's reply scope_summary: one-paragraph description of the work budget_band: 'under_5k' | '5k_25k' | '25k_100k' | '100k_plus' | 'open' — or any free-text dollar figure

About MCP

The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.

Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.

Work with this as data

Every MCP server here is available over the APIs.io API and to AI agents over MCP.

curl "https://apis.io/api/v1/mcp/tessa-mcp-server"

curl "https://apis.io/api/v1/mcp?limit=25"