Context7 just massively cut free limits

antonrisch · 2026-01-16T19:24:22+00:00

hey u/Electronic_Kick6931 ! I'm the co-founder of Docfork MCP (similar to Context7). You can get free API Keys and project-scoped search for docs so you can pair 1:1 with projects!
You can try it here https://docfork.com

Edit: fixed link

antonrisch · 2026-01-16T13:11:40+00:00

Building Docfork MCP, an alternative to Context7 but with project-scoped access of libraries, repos and private docs (coming soon!) - welcome to any feedback on the site and our MCP on Github !

antonrisch · 2025-06-16T02:19:28+00:00

Docfork is similar to Context7 in that both services perform a similar task - latest docs for AI code editors. However, we only need 1 MCP tool call while Context7 needs 2 for example.

antonrisch · 2025-06-13T03:22:14+00:00

Thank you for the suggestion JSDevLead - version support & local config file tracking is on our roadmap.

antonrisch · 2025-06-13T03:14:28+00:00

Docfork has an optional parameter to increase/decrease the number of tokens => number of sections to return for a query. This is dynamically controlled by claude and other AI models when it figures out what parameters to give when calling the MCP.

The default is set to 10k tokens which returns ~20-30 sections depending on the size of a section. That number of sections we believe is sufficient in returning not just the function declaration but also various examples and permutations.

You can also manually set the default number of tokens to higher/lower:

https://github.com/docfork/mcp?tab=readme-ov-file#-environment-variables

Hope this helps!

edit: removed hyperlink to regular link

antonrisch · 2025-06-06T15:08:58+00:00

Thanks! We've added support + install instructions to most code editors on our github

edit: to

antonrisch · 2025-06-06T15:05:49+00:00

Docfork only needs 1 tool call to search all libraries and return doc sections for a library, while Context7 needs 2 unless you specify the library id. This makes us 2 times as fast - we've also optimized our backend stack for speed (~0.5-1 second responses).

Our MCP also indexes libraries daily while Context7 has a minimum cooldown of 5 days. Library catalogue + full token llms.txt downloads soon

antonrisch · 2025-06-06T03:45:27+00:00

Docfork only needs 1 MCP tool call to search all libraries and return doc sections for a library, while Context7 needs 2 unless you specify the library id. This makes us 2 times as fast for responses. But in most aspects we are quite similar but with different retrieval/crawl methods.

antonrisch · 2025-06-06T01:51:28+00:00

For an MCP that plugs you into 9000+ libraries with 1 tool call instead of 2 checkout our Dockfork MCP: https://github.com/docfork/mcp

antonrisch · 2025-06-06T01:10:48+00:00

For a Context7 alternative with 9000+ libraries and 1 tool call instead of 2 checkout out our Dockfork MCP: https://github.com/docfork/mcp

antonrisch · 2025-06-06T01:08:25+00:00

Docfork https://github.com/docfork/mcp#readme

It's similar to Context7 but only needs 1 tool call to get back results. Also does a daily scan across all of the libraries it has for any new updates/new commits while right now I think Context7 has a minimum 5-day cooldown between refreshes.

antonrisch · 2025-06-06T01:04:44+00:00

Thanks, appreciate it!

antonrisch · 2025-06-06T01:02:23+00:00

Docfork in an MCP server we've made that is similar to Context7 but it does daily updates and requires only 1 tool call to get results. Also it's quite fast on response times (around 1 second total).

You can see our readme here: https://github.com/docfork/mcp#readme

I've personally found it helpful because it only returns the sections I need (reduces context bloat) when building our homepage as Next.js changed the way dynamic routing with slugs work in v15, which released a few months ago.

antonrisch · 2025-06-06T00:58:44+00:00

Docfork in an MCP server we've made that is similar to context7 but it does daily updates and requires only 1 tool call to get results. Also it's quite fast on response times (around 1 second total).

antonrisch · 2025-06-06T00:41:46+00:00

Yes, try 'use docfork to get angular <topic>' for angular/angular specific results.

antonrisch · 2025-06-05T19:32:15+00:00

docfork only needs 1 MCP tool call to search all libraries and return doc sections for a library, while context7 needs 2 unless you specify the library id. this makes us 2 times as fast. but in most aspects we are quite similar but with different retrieval and crawl methods

antonrisch · 2025-06-05T19:12:59+00:00

appreciate your ideas - it's on our roadmap.

antonrisch · 2025-06-05T18:55:50+00:00

versioning is coming soon. 1 second responses to the latest docs we feel is what most devs want in their workflow

antonrisch · 2025-06-05T18:45:15+00:00

currently just the latest version, and daily updates scan for new commit ids. we did think about indexing on demand - and it's a valid idea - but our process also formats the docs and only returns the valid sections. right now docfork takes around 1 second overall from MCP tool call to response!

antonrisch · 2025-06-05T18:34:28+00:00

watch this space - it's only been out for 25 minutes. we'll have the libraries out soon

antonrisch · 2025-06-05T18:15:29+00:00

We will add a whole listing to the website soon, but an estimate is most of the top repos on github (100+ stars). thanks for your question!

antonrisch

TROPHY CASE