TESSA Marketing & Technology MCP Server

TESSA's AI interface: services, case studies, AI-readiness audits, professional services directory.

Tools

Last Updated

Nov 2, 2026

What is the TESSA Marketing & Technology MCP Server?

The TESSA Marketing & Technology MCP server gives AI agents structured, permission-aware access to TESSA Marketing & Technology through the Model Context Protocol. With 10 pre-built actions, agents can read, create, and update TESSA Marketing & Technology data on behalf of authorized users.

Willow ships the TESSA Marketing & Technology MCP server as part of an enterprise control plane. Every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to a full audit trail, and integrates with Splunk and Loki for SIEM visibility. Connect from Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, or any custom agent. Install once, distribute org-wide, and see exactly how TESSA Marketing & Technology is being used by every AI agent in your stack.

Tools

get_services

Returns TESSA's full service catalog (SEO, paid media, web/app development, AI agent readiness, accessibility, and more). 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 [email protected] + [email protected] (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

Customize Tools

Edit descriptions, modify arguments, select tools, or add new ones

Set Up Your TESSA Marketing & Technology MCP Server in Minutes

Add the following configuration to your MCP client. Authentication is handled via OAuth. Compatible with Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, and any MCP-compatible agent.

Claude Desktop

claude_desktop_config.json

{
  "mcpServers": {
    "willow-tessa-marketing-technology": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/tessa-marketing-technology"
    }
  }
}

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "willow-tessa-marketing-technology": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/tessa-marketing-technology"
    }
  }
}

Claude Code

CLI

claude mcp add willow-tessa-marketing-technology --transport http https://<org>.mcp-s.com/mcp/mcp/tessa-marketing-technology

n8n

HTTP Request Node

{
  "url": "https://<org>.mcp-s.com/mcp/mcp/tessa-marketing-technology",
  "method": "POST"
}

Or click "Install with Willow" above to set up automatically with SSO and RBAC preconfigured.

Enterprise Governance for TESSA Marketing & Technology

Willow adds the layer TESSA Marketing & Technology and every other SaaS doesn't ship out of the box: every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to full audit logs, and detects shadow AI usage across your stack. One MCP gateway. Any agent. Every tool.

TESSA Marketing & Technology MCP Server FAQ

What is the TESSA Marketing & Technology MCP server?

The TESSA Marketing & Technology MCP server is a Model Context Protocol implementation that lets AI agents like Claude, Cursor, and ChatGPT read and write TESSA Marketing & Technology data through a standardized interface. Willow hosts and governs this server so enterprises can roll it out without a security review backlog.

How is Willow's TESSA Marketing & Technology MCP server different from the official one?

The official TESSA Marketing & Technology MCP server is scoped to a single user's account and does not include enterprise governance. Willow's version adds SSO, RBAC, audit logging, shadow AI detection, and centralized control over which actions agents can take across the entire org.

Which AI clients work with the TESSA Marketing & Technology MCP server?

Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code with MCP support, n8n, and any custom agent built with OpenAI Agents SDK, LangChain, Vercel AI SDK, or Anthropic SDK.

Is the TESSA Marketing & Technology MCP server secure? How does Willow handle authentication?

Every call runs behind your existing SSO (Okta, Azure AD). Per-user OAuth scopes the agent to exactly what that user can do in TESSA Marketing & Technology, nothing more. No credentials reach the LLM. Every action writes to an audit trail.

Can I limit which TESSA Marketing & Technology actions agents can take?

Yes. Willow lets you scope agents to specific actions, specific projects, or specific environments. Toggle actions on or off in the dashboard, or enforce policy via infrastructure-as-code through GitHub.

How do I detect shadow TESSA Marketing & Technology MCP servers in my org?

Willow's browser extension and discovery service surface unmanaged MCP servers, skills, and AI agents across the org. If a developer installed an unapproved TESSA Marketing & Technology MCP locally, you'll see it.

What does the TESSA Marketing & Technology MCP server cost?

Pricing depends on org size and deployment model (SaaS, dedicated cloud, self-host). See withwillow.ai/pricing or contact sales for a quote.

How do I install the TESSA Marketing & Technology MCP server with Willow?

Install via the Willow Connect Panel in one click, or paste the JSON snippet above into your Claude Desktop, Cursor, or Claude Code config. SSO and RBAC inherit from your existing Willow setup.