Factsets MCP Server
Give your agent a local, self-maintaining knowledge base that survives sessions instead of re-pasting project context every time.
Overview
io.github.joshua-auchincloss/factsets is an MCP server for the Build phase that offers agents a local persistent self-maintaining knowledge base over stdio.
What is this MCP server?
- Local, persistent knowledge base designed for AI agents (Factsets MCP Server v0.2.0)
- Self-maintaining fact storage so agents can add and refresh structured knowledge over time
- npm package factsets with npx mcp-server entry and stdio transport
- Fits long-horizon solo builds where context drift is the main tax
- Complements chat history with queryable facts rather than one giant system prompt
- Factsets MCP Server version 0.2.0 on npm registry
- Stdio transport with npx mcp-server launch pattern
- Repository: github.com/joshua-auchincloss/factsets
Community signal: 1 GitHub stars.
What problem does it solve?
Long agent sessions lose project truth when context windows reset and nothing structured persists between runs.
Who is it for?
Solo builders running agents daily on one codebase who want durable facts without standing up a team wiki.
Skip if: Teams that need shared cloud KB with SSO, audit trails, and human editorial workflow out of the box.
What do I get? / Deliverables
Agents can store, retrieve, and maintain facts locally so later phases reuse the same grounded project memory.
- Local persistent factsets agents can query during coding
- Self-maintained knowledge that reduces repeated context dumps
- MCP tools wired into your agent config for ongoing updates
Recommended MCP Servers
Journey fit
Persistent agent memory is introduced when you wire tooling during Build, then pays off across Ship, Grow, and Operate. Factsets is agent infrastructure—canonical placement is build → agent-tooling as the MCP surface for structured memory.
How it compares
Agent-local knowledge MCP, not a hosted Notion sync or a single prompt-injection skill.
Common Questions / FAQ
Who is Factsets MCP for?
Developers using Claude Code or similar agents who want persistent structured memory on their own machine.
When should I use Factsets MCP?
Early in a build when context repetition hurts velocity, and through operate when facts must stay current after changes.
How do I add Factsets MCP to my agent?
Add the npm package factsets (0.2.0) as a stdio MCP server with npx and the mcp-server positional argument per registry metadata.