Normalized references
Search consistent metadata across project ecosystems and follow each record back to its repository.
Open-source decision workspace
Your technical references, ready for every build.
Sourcefolio turns public open-source metadata and your team’s adoption decisions into one reliable, AI-accessible workspace.
Project workspace connectedStreamable HTTP MCP · account scoped
Source-linkedRecords retain repository origins
Account-scopedPrivate workspace boundaries
Tool-readyTwelve focused MCP operations
Product
Keep project context useful, current, and close to the work.
Research public projects, record the release details your team cares about, and make those references available to development tools without another tab.
Shared technical notes
Save versions, licenses, release dates, and evaluation notes in an isolated team workspace.
Built for AI workflows
Read and update references through a focused remote MCP server with explicit permissions.
Your workflow
Turn one project evaluation into reusable team context.
Sourcefolio fits between technical research and implementation, preserving the decision that otherwise disappears into chat, tickets, and documents.
Research the project
Start from normalized public metadata and follow the repository source to validate details.
Capture the decision
Save the selected version, license, release date, and your team’s adoption rationale.
Bring it into the build
Give developers and AI tools the same approved context through your private MCP workspace.
Public catalog
A useful baseline before your team adds context.
Sourcefolio maintains a compact catalog of commonly evaluated open-source projects. Private workspace records never appear here.
Zodnpm4.1.12MIT
Fastifynpm5.6.2MIT
DjangoPyPI5.2BSD-3-Clause
MCP server
Connect Sourcefolio to the tools your team already uses.
The remote server uses MCP Streamable HTTP and per-developer keys. Keys are read-only by default and map to exactly one workspace.
{
"url": "https://mcp.sourcefolio.io/mcp",
"transport": "streamable-http",
"headers": {
"Authorization": "Bearer ${SOURCEFOLIO_API_KEY}"
}
}
1
Receive a developer key
Your workspace administrator issues a scoped key.
2
Add the endpoint
Configure your remote MCP client once.
3
Read integration documentationWork from project context
Search public records or open your private library.
Private beta
Give your team a durable open-source decision layer.
We are onboarding team workspaces through a private beta. Tell us about your workflow and we will provide a quote.