MCP integration
Use Bellwork data and workflows from an AI assistant
Bellwork's Model Context Protocol server gives compatible AI clients tools over the same authenticated application and API contracts used by the dashboard.
Endpoint and authentication
https://www.bellwork.ai/api/mcp/bellwork/mcpMCP clients authenticate through OAuth. Direct API integrations should use API keys instead.
Common tools
| Goal | Tools |
|---|---|
| Discover seller profiles | list_profiles, create_profile, update_profile |
| Search the catalog | search_districts, search_schools, search_contacts |
| Find timely opportunities | search_signals, search_rfps, get_opportunities |
| Keep watch on an entity | follow_entity, unfollow_entity |
| Build and read research | create_brief, get_brief |
| Build CRM-ready tables | create_table, add_column, run_column, show_table |
| Draft outreach | generate_email |
Tool discovery in your MCP client is authoritative; Bellwork adds tools without requiring a protocol endpoint change.
Brief workflow
create_brief is an idempotent asynchronous operation. It reuses a ready brief,
does not duplicate a current build, and retries a failed or stale build. Call
get_brief to read the finished dossier or inspect its progress.
Following still starts a brief automatically. Enterprise/internal clients can
also call create_brief without following; free clients must follow first.
Pagination
Search tools expose bounded pages so a large catalog or nightly signal feed does not flood the model's context window. Ask the assistant to narrow by time, state, entity, or query first, then continue through pages only while the response indicates more results.
Rate limits
Bellwork API request limits and retry behavior
Current rolling AI capacity GET
Returns a coarse state and a renewal date — deliberately never a balance, a count, or a percentage. Metered AI actions (chat, enrichment runs, and contact finds) draw against the trailing 168-hour allowance on the free tier. Each action returns exactly seven days after it was reserved; there is no calendar reset. Briefs are recorded but unmetered because follow slots already bound them. Enterprise and internal are unmetered and report `metered: false`. Clients should show nothing while `comfortable`, a quiet notice at `low`, and the upgrade path at `exhausted`. Requests refused for want of allowance return 402 from the acting endpoint, not from here.