
Factsets MCP Server
io.github.joshua-auchinclossPublished by GitHub account joshua-auchinclossv0.2.0Updated Nov 3, 2026
An MCP server that provides a local, persistent, self-maintaining knowledge base for AI agents
Overview
Local SQLite-backed knowledge base for AI agents, storing facts, cached resources, skills and execution logs that persist across sessions.
- What you can do
- Add, search, verify, update, delete and restore tagged facts with source tracking
- Register resources with cached snapshots, search them, refresh snapshots and flag stale ones
- Create, search, link and sync markdown skill documents and inspect their dependency graph
- Record and query command, test and build execution logs
- Manage tags, configuration values and user preferences
- Build context from tags and fetch setup, maintenance and refresh guides
- When to use it
- Useful when you want an assistant to remember project knowledge between sessions, keep notes on external files and APIs with staleness tracking, and store reusable procedural skills. Best for long-running projects where context is repeatedly rebuilt.
- Requirements
- Runs as a local stdio process via npx, bunx or pnpm dlx (Node.js or Bun runtime). Uses a local SQLite database, optionally set with a database URL flag. No accounts, API keys or environment variables are declared. A one-time setup prompt or tool call is recommended to integrate it into a project.
Installation
In SourceWeft
- Open Factsets MCP Server in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Factsets
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.
Features
- 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
Installation
Quick Start
As MCP Server
Add to your MCP client configuration (Claude Desktop, GitHub Copilot, Cursor, etc.), using bunx, npx or pnpm dlx accordingly:
Or run directly:
First-Time Setup
After adding Factsets to your MCP client, run the setup prompt to integrate it into your project:
In a supported IDE: Type /mcp.factsets.setup in the chat to run the guided setup
In other clients: Call the get_setup_guide tool or use the setup prompt
The setup guide will:
- Analyze your project structure and establish baseline facts
- Configure the skills directory for your AI client
- Create or update
AGENTS.mdwith Factsets instructions - Migrate any existing skills with Factsets integration
- Register key configuration files as resources
This one-time setup ensures agents have full context on every future interaction.
CLI Commands
The --client flag configures where skill files are stored (e.g., github-copilot -> .github/prompts/skills/). If you want to change clients / your skill directory, do so through your agent which will migrate skills for you.
See Configuration Guide for all options.
Core Concepts
MCP Tools
Facts
Resources
Skills
Execution Logs
Tags
Configuration
User Preferences
Maintenance
Context & Guides
MCP Prompts
Documentation
- Configuration Guide - CLI flags, client setup, and skills directory
- Design Reference - Full API documentation
- Concept - Philosophy and design rationale
- Agent Workflow - How agents use Factsets
Development
Source: README.md at commit 1cf149c
Tools
0Version history
1- v0.2.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts