Plantik

MCP Console — AI skill for Claude Code

AI community

Self-hosted MCP context server for AI coding agents — project docs, per-branch tasks, skills and templates as markdown, with a web console (Nuxt 4).

How to install MCP Console

This entry records only its repository, not the path inside it, so there is no exact command to give. Open Plantik/mcp-console and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What MCP Console does

Self-hosted MCP context server for AI coding agents — project docs, per-branch tasks, skills and templates as markdown, with a web console (Nuxt 4).

Alternatives in AI

Agentrq — AgentRQ: Human-in-loop realtime conversational task manager for AI Agents 1.1k ★
CliRelay — Self-hosted AI gateway for coding CLIs — one OpenAI/Claude/Gemini/Codex-compatible endpoint, with a multi-tena 1k ★
Free GPT4 WEB API — Not just GPT4 690 ★

README

MCP Console

A self-hosted **context server for AI coding agents**. It stores your project docs, coding skills and per-branch task plans as plain markdown, serves them to Claude Code (or any MCP client) over the [Model Context Protocol](https://modelcontextprotocol.io), and gives you a web console to browse and edit everything.

Projects — documentation pages agents load on demand (index, architecture, deploy, …)
Tasks — one markdown plan per git branch, with an active → pending → history lifecycle, so an agent can resume where the last session stopped
Skills — team conventions agents load only when relevant (progressive disclosure keeps token use low)
Templates — per-stack scaffolds used when creating a new project
Knowledge base — self-contained HTML landing pages / explainers

Built with Nuxt 4, Nuxt UI, Nuxt Content and the official MCP TypeScript SDK. Content lives on disk under `content/` — no database to migrate, easy to back up or keep in git.

Quick start

Requires Node 22+ and pnpm.

pnpm install
cp .env.example .env      # set MCP_USERNAME / MCP_PASSWORD (and MCP_TOKEN)
pnpm dev                  # console: http://localhost:3000  ·  MCP: http://localhost:3000/mcp

Sign in with the credentials from `.env`. The repo ships with example content (`example-app` project, two skills, one landing) so every screen has something to show.

Connect Claude Code

Copy `.mcp.json.example` to `.mcp.json` in the repo you want agents to work in (or run the CLI equivalent):

claude mcp add --transport http mcp-console http://localhost:3000/mcp \
  --header "Authorization: Bearer $MCP_TOKEN"

Then tell the agent how to use it, e.g. in that repo's `CLAUDE.md`:

## Session start
1. `get_project_context("my-project", "index")`
2. `list_skills` — load only the skills relevant to the task
3. `get_task("my-project", "")` — if missing, `upsert_task` with a plan
4. As you work: `chec