0
2 commits
updated Oct 3, 2026
See what people are saying
README
claude-connectors-vs-mcp-vs-skills-vs-plugins-example
An example project for the article "Claude Connectors vs MCP vs Skills vs Plugins - What Goes Where". It covers everything that's added on the machine, so it works in Claude Code only:
| File | What it is |
|---|---|
.mcp.json | A local MCP server (DBHub) that queries a local Postgres database |
CLAUDE.md | Instructions that load into every session |
.claude/skills/release-notes/SKILL.md | A project skill that loads only when a task needs it |
plugins/blog-tools/ | A plugin that bundles the Notion MCP server with a skill |
.claude-plugin/marketplace.json | Turns this repo into a marketplace, so we can install the plugin |
Connectors aren't here because they live on the claude.ai account (Customize > Connectors), not in a repo.
Usage
Start the database (Postgres on port 5433, with a read-only reader user):
docker compose up -d
Then run claude in the repo and approve the db server from .mcp.json. Now we can ask Claude something like "Which posts aren't published yet?".
The release-notes skill works on merged pull requests, so it's meant for a repo of our own. Copying .claude/skills/release-notes/ there lets us trigger it directly with /release-notes.
To install the plugin:
/plugin marketplace add nitayneeman/claude-connectors-vs-mcp-vs-skills-vs-plugins-example
/plugin install blog-tools@example-marketplace
The plugin's Notion server needs its own authorization, which /mcp handles.
Where Each Piece Came From
/mcplists the servers:dbcomes from.mcp.json,notionfrom the plugin, and anything with aclaude.aiprefix is a connector./skillslists the skills:release-notesfrom the project andblog-postfrom the plugin.
Similar repos
0
2 commits
updated Oct 3, 2026
See what people are saying
README
claude-connectors-vs-mcp-vs-skills-vs-plugins-example
An example project for the article "Claude Connectors vs MCP vs Skills vs Plugins - What Goes Where". It covers everything that's added on the machine, so it works in Claude Code only:
| File | What it is |
|---|---|
.mcp.json | A local MCP server (DBHub) that queries a local Postgres database |
CLAUDE.md | Instructions that load into every session |
.claude/skills/release-notes/SKILL.md | A project skill that loads only when a task needs it |
plugins/blog-tools/ | A plugin that bundles the Notion MCP server with a skill |
.claude-plugin/marketplace.json | Turns this repo into a marketplace, so we can install the plugin |
Connectors aren't here because they live on the claude.ai account (Customize > Connectors), not in a repo.
Usage
Start the database (Postgres on port 5433, with a read-only reader user):
docker compose up -d
Then run claude in the repo and approve the db server from .mcp.json. Now we can ask Claude something like "Which posts aren't published yet?".
The release-notes skill works on merged pull requests, so it's meant for a repo of our own. Copying .claude/skills/release-notes/ there lets us trigger it directly with /release-notes.
To install the plugin:
/plugin marketplace add nitayneeman/claude-connectors-vs-mcp-vs-skills-vs-plugins-example
/plugin install blog-tools@example-marketplace
The plugin's Notion server needs its own authorization, which /mcp handles.
Where Each Piece Came From
/mcplists the servers:dbcomes from.mcp.json,notionfrom the plugin, and anything with aclaude.aiprefix is a connector./skillslists the skills:release-notesfrom the project andblog-postfrom the plugin.