Searcher Os MCP server
{
"mcpServers": {
"searcher-os": {
"type": "http",
"url": "https://searcheros.ai/api/mcp/mcp"
}
}
}{
"mcpServers": {
"searcher-os": {
"type": "http",
"url": "https://searcheros.ai/api/mcp/mcp"
}
}
}{
"mcpServers": {
"searcher-os": {
"type": "http",
"url": "https://searcheros.ai/api/mcp/mcp"
}
}
}{
"servers": {
"searcher-os": {
"type": "http",
"url": "https://searcheros.ai/api/mcp/mcp"
}
}
}{
"mcpServers": {
"searcher-os": {
"type": "http",
"url": "https://searcheros.ai/api/mcp/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.0.1
What it does
Searcher OS MCP Server connects AI agents to the Searcher OS platform for acquisition entrepreneurs. It exposes 37 tools across 11 categories covering deal pipeline management, broker CRM, CIM analysis, deal feed search, and SBA loan modeling. It is intended for users on the Searcher or Deal Team plan who want to interact with their M&A workflow through an AI agent.
- Search the deal feed for businesses matching specific criteria such as industry, location, and financial thresholds, then track promising deals through a pipeline.
- Review and annotate CIM documents for a deal, including appending supplementary financials and flagging unusual add-backs.
- Model SBA 7(a) loan scenarios for a given purchase price and down payment, and receive a calculated DSCR.
Tools this server exposes
| Tool | Does |
|---|---|
| context | Provides a connectivity check plus a summary of the user's profile, buy boxes, pipeline, and feed statistics. |
| pipeline_view | Lists deals currently in the user's acquisition pipeline. |
| pipeline_create | Creates a new deal in the pipeline. |
| pipeline_update | Updates details on an existing pipeline deal. |
| pipeline_move | Moves a deal to a different pipeline stage. |
| pipeline_kill | Marks a pipeline deal as dead or removed. |
| feed_search | Searches the deal feed for businesses matching specified criteria. |
| feed_count | Returns a count of deals in the feed matching given filters. |
| feed_statistics | Returns aggregate statistics about the deal feed. |
| feed_save | Saves a deal from the feed for later review. |
| feed_dismiss | Dismisses a deal from the feed. |
| buy_box_list | Lists the user's defined acquisition criteria including price range, industry, and location. |
| inbox_list | Lists inbound broker emails in the inbox. |
| inbox_view | Views the content of a specific inbound broker email. |
| inbox_link | Links an inbound email to a deal in the pipeline. |
| inbox_ignore | Marks an inbound email as ignored. |
| broker_list | Lists brokers in the CRM. |
| broker_view | Views details for a specific broker. |
| broker_create | Creates a new broker record in the CRM. |
| broker_log_interaction | Logs an interaction with a broker. |
| cim_list | Lists CIM analyses available in the account. |
| cim_view | Views the analysis for a specific CIM. |
| cim_search | Searches within CIM documents. |
| cim_append_financials | Appends supplementary financial data to a CIM analysis. |
| confirmation_list | Lists write operations pending confirmation. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.