Open Source Directory

Open-Source AI Repos & MCP Servers

Curated directory of trending GitHub repositories, MCP servers, and AI agent skills for developers and researchers.

Updated Daily
Hand-Picked Quality
Free & Open Source

Featured Repositories

View All

Hand-picked open source projects driving AI forward.

openai/openai-agents-python
0

OpenAI's official lightweight Python framework for multi-agent workflows. Released April 2026 as OpenAI's answer to Microsoft Agent Framework and Google ADK. Small surface area, opinionated primitives, first-class tool calls against the OpenAI API. If you already ship on GPT and Responses API, this is the path of least resistance to multi-agent. The SDK ships four primitives: Agents (LLMs with instructions and tools), Handoffs (one agent delegating to another), Guardrails (input and output validation), and Sessions (automatic conversation history). That is the entire mental model. Compare to LangGraph's graph-of-nodes complexity or Microsoft's full stack with DevUI and MCP Apps, and the OpenAI SDK reads like a deliberate reduction. No orchestration DSL, no registry, no runtime UI. Just Python. Early ecosystem response has been strong — the repo has trended on GitHub since launch and is already on PyPI. Tracing is built in with OpenAI's dashboard. MCP support is shipped. Local model compatibility lands through LiteLLM. The bet is that a smaller framework wins developer mindshare because it gets out of the way. The critique: minimalism cuts both ways. There is no built-in DevUI like Microsoft Agent Framework 1.0 ships, no visual tool-call debugger, no LTS commitment. If you need a production-ready agent platform with enterprise governance, you are on your own for observability, deployment, and versioning. For prototyping and for OpenAI-first stacks, it is the cleanest option.

Python
0

Latest MCP Servers

View All

Connect your agents to external tools and data sources.

You know the workflow. Write code locally. Copy into a Colab notebook. Run it for GPU access. Find a bug. Copy back to your editor. Fix. Paste again. Repeat until your sanity erodes.Google Colab MCP Server ends that workflow. Any AI agent that speaks Model Context Protocol — Claude Code, Cursor, Windsurf, Copilot, Gemini CLI — can now control Colab notebooks directly. The agent creates the notebook, writes the cells, installs dependencies, runs the code, and iterates. You watch the notebook being built in real-time.Google's Colab team published the server at github.com/googlecolab/colab-mcp. Apache 2.0 license. Python 3.11+. Free.What It Actually DoesThe server exposes Colab functionality as MCP tools. An agent can:Create new .ipynb files with a specified runtime (CPU, GPU, TPU)Inject markdown cells for documentation and section headersDraft and execute Python code cells, receiving outputs including errors and stack tracesInstall pip dependencies and apt packages in the runtimeRearrange cells for logical flow as the notebook evolvesRead outputs and iterate based on resultsSave and share the completed notebookThe agent writes the notebook the way a human would — incrementally, watching what works, adjusting what does not. The difference is speed. What takes a human 30 minutes of copy-paste-run-debug takes the agent three minutes.InstallationOne command with uv: uvx install colab-mcp. Then configure your MCP client (Claude Desktop, Cursor, Gemini CLI) to point at the installed server. The README has copy-paste configs for each major client.The server authenticates to Colab through your Google account. On first use, you grant the MCP server access to your Drive (where .ipynb files live) and Colab's runtime API. Standard OAuth flow, revocable from your Google account settings.The GPU Access AngleThis is where it gets interesting. Colab provides free GPU runtimes (T4, A100 when available for Pro users). Before this server, your AI agent on your laptop had no practical path to GPU compute for ML workloads. Now it does.A workflow that was impossible yesterday is now trivial: ask Claude Code to train a small PyTorch model on MNIST, iterate on the architecture, and tune hyperparameters. The agent launches a GPU runtime in Colab, runs the training, reads the results, adjusts, and repeats. Your local machine never runs a single training step.Why Google Released ThisGoogle's 2026 strategy has been relentlessly open. The Gemini CLI went open-source. The Android ADK is MCP-compatible. Firebase is publishing MCP integrations. Now Colab. The pattern: Google is betting that becoming the default AI infrastructure for any agent is more valuable than protecting proprietary tooling.This is an opposite bet from Anthropic's Claude-first approach. Anthropic wants agents built on Claude. Google wants Google infrastructure used by agents built on any model. The Colab MCP Server is a clean example: it works with Claude, not just Gemini. Google benefits when anyone's agent runs on Colab's GPUs, not just Gemini-powered agents.Use Cases That Make SenseML experimentation: ask an agent to run a hyperparameter sweep, compare architectures, produce a plot. Colab's free GPU tier handles the compute.Data exploration: hand a CSV to an agent, ask it to 'find the five most interesting patterns.' The agent loads the file into a Colab notebook, runs pandas and seaborn cells, and produces a written summary with supporting visualizations.Rapid prototyping: 'Prototype a semantic search over this document set using sentence-transformers.' The agent installs dependencies, embeds the documents, sets up the search, and produces a working demo. You watch the notebook being built.Reproducible research: agents build notebooks that include the full reasoning and experimentation trail, not just the final code. The notebook is the audit log.LimitationsThe server authenticates to a single Google account at a time. Multi-tenant deployment requires workarounds. Teams that want to share agent-generated notebooks across users face permission complexity.Colab's free tier has compute quotas. Agents that run long training jobs or large hyperparameter sweeps can hit the quota mid-run. The server does not currently queue or retry against the quota wall — the agent has to handle the error gracefully.Runtime state is tied to the notebook's active session. If Colab disconnects (idle timeout, browser close), the runtime variables are lost. The agent can re-execute cells, but any expensive computation is repeated.The server is new — version 0.1.0 at launch. Expect breaking changes over the next few minor versions as Google iterates based on usage.For more MCP servers, browse repos.skila.ai/servers. For AI coding and agent tools, check tools.skila.ai. For articles on Model Context Protocol adoption, visit news.skila.ai.

MCP serverGoogle Colab MCPModel Context Protocol Colab+4
other

n8n-MCP turns your AI coding assistant into an n8n workflow automation expert. It bridges the Model Context Protocol with n8n's entire node ecosystem: 1,396 nodes (812 core + 584 community), 2,700+ workflow templates, and 265 AI-capable tool variants.The practical difference: before n8n-MCP, asking Claude Code to build an n8n workflow was a coin flip. The model would hallucinate node names, invent non-existent parameters, and produce workflows that failed validation. n8n-MCP eliminates that by feeding the AI comprehensive, accurate documentation for every node, operation, and property.The creator, Romuald Czlonkowski, claims it reduces workflow creation time from 45 error-prone minutes to 3 flawless minutes. That number comes from community reports, not formal benchmarks. But the architecture supports it: 99% property coverage, 87% documentation availability, and 2,646 pre-extracted real-world configurations from popular templates.How It WorksThe MCP server exposes n8n documentation as structured tools that AI assistants can query. When you ask Claude Code to "build a workflow that triggers on a new Stripe payment and sends a Slack notification," the server provides exact node configurations, credential schemas, and expression syntax. The AI does not guess. It looks up the correct parameters.A Chat Agent feature lets you describe automations in plain language and receive production-ready workflows. Diff-based updates allow modifying existing workflows without rebuilding from scratch. Real-time monitoring and auto-validation catch errors before deployment.Setup OptionsThe fastest path is the hosted dashboard at dashboard.n8n-mcp.com (free tier: 100 tool calls/day, 5 chat prompts/day). For self-hosting: npx, Docker, Railway, or local installation. The Supporter plan at 19 EUR/month gives 200 daily prompts and unlimited tool calls.Compatible AI ToolsWorks with Claude Code, Claude Desktop, Cursor, Windsurf, VS Code with GitHub Copilot, Gemini CLI, Kiro, Codex, and 15+ other AI development tools. The companion n8n-skills repository provides 7 Claude Code skills for deeper integration.LimitationsOperation coverage sits at 63.6%, meaning some node operations lack full documentationFree tier limits (100 calls/day) may be tight for heavy automation buildersCommunity nodes (584) have less reliable documentation than core nodesThe server provides documentation only. It does not execute workflows or manage n8n instances directly (use n8n-manager-for-ai-agents for that)Critical safety note from the maintainers: never edit production workflows directly with AI. Always test in development environments first and export backups before deployment.For more MCP servers, browse repos.skila.ai/servers. For AI workflow automation tools, check tools.skila.ai. For articles on AI-powered automation, visit news.skila.ai.

MCP n8n serverModel Context Protocoln8n workflow automation+3
other

The official Model Context Protocol filesystem server that gives Claude direct read and write access to files and directories on your local machine or server. Install it once and Claude can open files, create new ones, list directories, search across your codebase, and move or rename files — all without copy-pasting content into the chat window. It ships as part of the official MCP servers repository maintained by Anthropic, making it the most trusted and widely-deployed server in the ecosystem. Because you specify allowed directories at startup, Claude only ever sees what you explicitly permit — it cannot access /etc, your home folder, or any path outside the scope you configure.

filesystemfile-managementmcp+4
81,124
filesystem

Top AI Skills

View All

Equip your agents with specialized capabilities.

Browserbase just turned Claude Code into a real web agent. The browserbase/skills repo went live in October 2025 and exploded onto GitHub Trending the week of May 4-5, 2026 with a wave of new agent skills designed specifically for the Claude Code Agent SDK. 3,188 stars and 212 forks as of today. This is the production-grade browser-automation SDK that's been missing from the Claude Code ecosystem. You install the marketplace, pick the skills you need, and Claude gains real browser capabilities — not a sandbox, not a screenshot trick, but a full Browserbase remote session that can log into your accounts, scrape JavaScript-rendered pages, run adversarial UI tests, and deploy serverless browser functions. The 11 skills shipped today browser — CLI-driven web automation against remote Browserbase sessions. browserbase-cli — the official bb CLI for managing platform workflows from Claude. functions — deploy serverless browser automation to Browserbase's cloud, callable from any agent. site-debugger — diagnose and auto-fix failing automations. The skill that pays for itself in saved hours. browser-trace — capture full DevTools protocol traces. Critical for debugging flaky tests. safe-browser — local agent SDK with domain allowlist enforcement, so the agent can't wander off-policy. bb-usage — display real-time usage stats and cost forecasts inside Claude. cookie-sync — sync cookies from your local Chrome into a Browserbase session. The missing piece for "log in to authenticated pages" workflows. fetch — retrieve HTML or JSON from static pages. search — structured web search results, not just a markdown dump. ui-test — AI-powered adversarial UI testing. Feed it a git diff and it runs your changes against the live UI in a real browser. How to install One command inside Claude Code: /plugin marketplace add browserbase/skills Then install the browse plugin and restart Claude Code. Each skill is a folder under skills/ in the repo and each can be enabled independently. Why this matters The headline skill is ui-test. It takes a git diff, spins up a real browser, navigates to the affected page, and runs an adversarial test pass against your UI changes. That used to require a dedicated test engineer plus a CI pipeline plus Playwright/Selenium glue. Now it's one install. For frontend teams shipping multiple changes a day, this single skill changes the economics of testing. cookie-sync is the second sleeper hit. Headless browser agents have always struggled with authenticated pages — you either build a fragile credential injector, or you bake cookies into the agent's state. cookie-sync grabs them directly from your local Chrome profile. Claude can now legitimately log into your dashboards, scrape your data, file your tickets. How this differs from other Claude skills This is operational infrastructure, not opinionated configuration. Compare it to Matt Pocock's engineering skills (curated prompts and conventions for senior engineers) and Andrej Karpathy's single-file CLAUDE.md (prescriptive style guide). Those tell Claude how to think. Browserbase Skills give Claude what to do with a browser. Pairs with The parent platform: Browserbase — the cloud-browser infrastructure these skills run on. If you're not already on Browserbase, you'll want an account before installing — most of the skills require a remote session. Status Repo created October 12, 2025. Latest commit May 13, 2026. Active development from the Browserbase team. JavaScript primary language. No explicit license file in the repo as of today — the skills are published under Browserbase's standard terms, but if you're building commercial automation on top, confirm with their team.

Browserbase SkillsClaude Code web browsingClaude agent SDK+4
other

mattpocock/skills is Matt Pocock's personal .claude directory — the curated engineering skills he uses with Claude Code every day, lifted directly from his daily config and shipped as a repo.This is the counterpoint to Karpathy's CLAUDE.md moment. Where Karpathy gave the community one prescriptive file and let it ricochet across every greenfield project, Pocock ships a full directory — multiple skills, each scoped to a specific engineering task. TypeScript skills, Vitest skills, refactor skills, library-evaluation skills. It's what a Claude Code config looks like when a senior engineer has actually lived with the tool for months.Why it spikedTwo reasons, both real:1. The community wants worked examples, not theory. Anthropic's skill docs explain the mechanism. Pocock's repo shows what a working skill actually contains — the prompt shape, the file references, the trigger criteria. People clone, adapt, and run.2. TypeScript developers are the highest-leverage Claude Code audience right now. Pocock built his reputation on TypeScript pedagogy. His skills are TS-flavored — type narrowing, generic constraints, library refactors. That's the same crowd already using Claude Code aggressively, so the fit is unusually tight.Installgit clone https://github.com/mattpocock/skills .claude # or pick individual files and drop into your existing .claude/skills/Read each skill before activating — they're opinionated about TypeScript style and may not match every codebase.What's insideType-narrowing review skill — flags any escapes and suggests narrower typesLibrary evaluation skill — structured framework for picking a depRefactor playbooks — TS-specific patterns for safely moving codeTest writing skill — Vitest-flavored, behaviour-firstSeveral editorial skills for technical writing tasksCompare withAndrej Karpathy Skills — the single-file CLAUDE.md approach, broader and more philosophicalClaude Skills (Rezvani) — a 245+ skill bundle for breadth contrastFor the broader 2026 ranking question ("which AI tools and approaches are actually winning right now?"), see our today-dated speed ranking on AI image generators — the same instinct applies: small, opinionated, focused beats big and generic.

matt-pocock-skillsclaude-code-skillstypescript-claude-skills+1
intermediatedevelopment

Anthropic's official open-source skill bundle for financial services hit GitHub on May 5, 2026 and pulled 9.3k stars in under 48 hours. The repo at anthropics/financial-services ships under Apache 2.0 and is the canonical reference for every Wall Street team standing up Claude-powered workflows in 2026. What is in the box: 10 named agent templates, 7 vertical skill bundles and 11 MCP data connectors, plus install scripts for Microsoft 365 (Excel, PowerPoint, Word) and a Claude Managed Agents cookbook for IT to deploy at scale. Three deployment surfaces — Claude Cowork plugins for desk users, Claude Code plugins for engineering teams, and Managed Agents for centralized rollout. Same code, different distribution. The 10 named agents cover the work analysts actually grind on: Pitch Agent (builds branded pitchbooks from comps and precedents), Meeting Prep Agent (client briefing packs), Earnings Reviewer (earnings calls and model updates), Model Builder (DCF, LBO and three-statement models in Excel), Market Researcher (industry overviews and competitive landscape), Valuation Reviewer (GP packages to LP reporting), GL Reconciler (general-ledger break detection and root-cause traces), Month-End Closer (accruals, roll-forwards, variance commentary), Statement Auditor (LP statement audits) and KYC Screener (document parsing plus rules engine). The 7 vertical skill bundles let you install the right scope for the right desk: financial-analysis (the core bundle — comps, DCF, LBO, three-statement models, deck QC, and all 11 data connectors), investment-banking (CIMs, teasers, merger models), equity-research (earnings notes, initiations, thesis tracking), private-equity (sourcing, screening, IC memos), wealth-management (client reviews, rebalancing, tax-loss harvesting), fund-admin (GL recon, accruals, NAV tie-out) and operations (KYC parsing and rules evaluation). The 11 MCP data connectors are the part that matters for production. Daloopa, Morningstar, S&P Global, FactSet, Moody's, MT Newswires, Aiera, LSEG, PitchBook, Chronograph and Egnyte all ship as first-class integrations on day one. Most of those vendors announced same-day support; Moody's launched its own MCP app the same morning. Anthropic did not stand this up alone — the data providers wired in alongside the launch, which tells you Wall Street's data stack has converged on MCP as the integration spec. The disclaimer woven through every skill is Anthropic's clearest signal that the team read the regulatory landscape before shipping. None of these agents auto-trade, auto-onboard customers or close books unsupervised. The agents draft analyst work product for human review and sign-off only. That is the right design for a regulated category — and it lines up with the Nature Human Behaviour finding that human-AI combinations on decision-making tasks need explicit verification steps to avoid degrading accuracy. Pairing notes: the README points to Claude Opus 4.7 as the recommended model. Opus 4.7 leads the Vals AI Finance Agent benchmark at 64.37%, ahead of every other publicly evaluated model. If you are running Sonnet for cost reasons, the agents work but expect lower first-pass accuracy on the modeling and audit tasks. Honest critique: this is reference code, not turnkey software. Installation is straightforward (the marketplace command is claude plugin marketplace add anthropics/claude-for-financial-services), but customizing the prompts, wiring the data connectors to your firm's authentication, and producing audit-ready output that survives compliance review is non-trivial. Budget engineering time for the integration, not just the install. And remember the productivity research: stacking all 10 agents on top of an existing Bloomberg + Excel + FactSet workflow puts you well into the brain-fry zone. Where it fits on Skila: the productivity context for these agents is in our analysis of why more AI tools makes your team slower. For document retrieval that pairs cleanly with the Earnings Reviewer and Model Builder agents, see PageIndex and PageIndex MCP. For governance across the resulting agent fleet, see Microsoft Agent 365.

Claude finance skillsAnthropic financial services pluginsagent skills banking+5
intermediateother

Weekly AI Digest