Factsets MCP Server

An MCP server that provides a local, persistent, self-maintaining knowledge base for AI agents. The factsets mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 6 defined tools rather than through you.

What it actually does

A self-maintaining knowledge base for AI agents, exposed via the Model Context Protocol (MCP). Manages facts (atomic knowledge), resources (cached external content), skills (procedural markdown), and execution logs (command history) using SQLite.

• Persistent Context — - Knowledge survives across sessions
• Self-Maintaining — - Staleness detection with refresh instructions
• Tag-Based Organization — - Flexible categorization and retrieval
• Skill Documents — - Markdown files for procedural knowledge
• User Preferences — - Configurable output style and agent behavior
• MCP Protocol — - Standard interface for AI tool/prompt definitions

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Its toolset

Everything the assistant can do here goes through one of these:

• Facts — The Facts tool exposed by this server
• Resources — The Resources tool exposed by this server
• Skills — The Skills tool exposed by this server
• Tags — The Tags tool exposed by this server
• Configuration — The Configuration tool exposed by this server
• Maintenance — The Maintenance tool exposed by this server

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the factsets mcp server does with a few real requests.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Factsets's toolset — Facts, Resources, Skills and 3 more — is a fair guide to whether it matches your workflow. It is maintained by joshua-auchincloss; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.