MCP

Connect HomeForce MCP

Create a HomeForce agent API key, connect the HomeForce MCP endpoint to your AI client, and choose which tools/scopes that key can use. The MCP server publishes the tool shapes; the API key authorizes access to your workspace. Current toolset: homeforce-mcp.v1.

Hosted MCP endpoint

https://mcp.homeforce.ai

Versioned manifest:

https://mcp.homeforce.ai/manifest

Use a bearer token issued by HomeForce:

Authorization: Bearer <HOMEFORCE_AGENT_API_KEY>

Current safe tools

homeforce_list_email_templates
homeforce_get_email_template
homeforce_create_email_template_draft
homeforce_update_email_template_draft
homeforce_publish_email_template
homeforce_send_email_template_test
homeforce_list_email_campaigns
homeforce_get_email_campaign
homeforce_get_ai_provider_status
homeforce_create_email_campaign_draft
homeforce_preview_email_campaign
homeforce_request_email_campaign_approval

Template publishing and one-off test sends are exposed. Campaign approval, deletion, bulk sends, and provider credential mutation are not exposed through the MCP wrapper.

Local stdio

HOMEFORCE_API_BASE_URL=https://api.homeforce.ai
HOMEFORCE_AGENT_API_TOKEN=...
npm run mcp:homeforce

Operations runbook

Create and rotate agent API keys from HomeForce Agent Access. New keys expire after 90 days by default.
Confirm a new key in MCP Activity before revoking the old key.
Rotate EmailIt or provider delivery credentials in the authenticated app UI, then send one test email.
Rotate OpenAI, Anthropic, and Grok BYOK credentials from Agent Access. Keep providers disabled unless model-backed drafting is intentionally enabled.
Provider secrets are encrypted at rest; admin reads show redacted values only.

Durable controls

agent_tool_events records workspace, key, tool, scope, result, status code, and latency for MCP-backed API calls.
agent_quota_counters tracks durable per-key usage windows.
Daily quota-protected scopes: email_templates:test_send and email_campaigns:draft.

Compatibility policy

Within homeforce-mcp.v1, HomeForce may add tools, optional inputs, and response fields. Required input changes, removed tools/scopes, or changed side-effect semantics require a new major toolset version. Deprecated v1 tools remain documented for at least 30 days before removal from a future major version.