Connect an AI client
Set up read-only MCP and explore its four supported tools.
Connect an AI client with MCP
MCP gives compatible AI clients four read-only tools for FilingSift coverage, filing lists, filing details and filing search. Other research operations use their documented REST endpoints. In your client's remote-server settings, choose Streamable HTTP, set the URL to https://api.filingsift.com/mcp, and supply Authorization: Bearer <your API key> through its protected credential field. Use a scoped key from API keys with filings:read for the connection (its current compatibility permissions also satisfy the search tool’s search:read check), not your password or browser cookie. A client must support custom authorization headers; an OAuth-only connection flow is not compatible with this API-key setup. Settings names vary by client.
| Tool | Use | Key scopes |
|---|---|---|
filingsift_coverage_status | Inspect the current coverage receipt | filings:read (MCP connection) |
filingsift_list_filings | List eligible filings with filters and cursor pagination | filings:read |
filingsift_get_filing | Read one indexed accession and its evidence | filings:read |
filingsift_search | Search bounded indexed passages | filings:read; search checks search:read, currently satisfied by compatibility |
First test: connect, list tools and call filingsift_coverage_status with {}. Expect the four tools above and a coverage receipt showing available records and measurement time. If the call returns an error, use the troubleshooting table below. In an AI client, ask: “Use FilingSift to find available AAPL filings, then search for debt disclosures and include the accession, source URL and evidence in your answer.” For a repeatable Node.js test, install npm install @modelcontextprotocol/client@2.3.1, save this as mcp-example.mjs and run node mcp-example.mjs with the secret environment variable set.
import { Client, StreamableHTTPClientTransport } from "@modelcontextprotocol/client";
const apiKey = process.env.FILINGSIFT_API_KEY;
if (!apiKey) throw new Error("Set FILINGSIFT_API_KEY in your server environment");
const client = new Client({ name: "filingsift-quickstart", version: "1.0.0" });
const transport = new StreamableHTTPClientTransport(
new URL("https://api.filingsift.com/mcp"),
{ requestInit: { headers: { Authorization: "Bearer " + apiKey } } }
);
try {
await client.connect(transport);
const { tools } = await client.listTools();
console.log(tools.map(tool => tool.name));
const result = await client.callTool({ name: "filingsift_coverage_status", arguments: {} });
if (result.isError) throw new Error("Coverage tool refused the request; inspect its REST error envelope");
console.log(result); // Inspect available records and their measurement time.
} finally {
await client.close();
}Usage: MCP is included in existing API plans without a separate fee or allowance. Initialization and tool discovery do not consume monthly API requests. Each data-tool invocation makes one REST operation and consumes one monthly API request plus the normal query-cost units. One prompt can call several tools. Plan limits stop requests without automatic overage charges. The example above makes one metered tool call.
MCP cannot change accounts, save research, enable alerts, enqueue ingestion or start exports. Company permissions, API scopes, usage and indexed coverage still apply. All plans include all available indexed filing history for permitted companies. Inspect isError and the returned REST envelope when a tool refuses; do not treat a connected client or a successful tool list as proof that every data request is permitted.