Skip to content

feat: adding claude code mcp guide#204

Merged
sriramveeraghanta merged 2 commits intomasterfrom
feat-add-mcp-claude-code-guide
Feb 5, 2026
Merged

feat: adding claude code mcp guide#204
sriramveeraghanta merged 2 commits intomasterfrom
feat-add-mcp-claude-code-guide

Conversation

@sriramveeraghanta
Copy link
Member

@sriramveeraghanta sriramveeraghanta commented Feb 4, 2026

Add MCP Server Documentation for Claude Code Integration

Summary

This PR adds comprehensive documentation for integrating Plane with Claude Code using the Model Context Protocol (MCP), enabling AI-assisted project management directly from the terminal.

Changes

New Documentation

  • docs/dev-tools/mcp-server-claude-code.md - Complete guide for setting up and using the Plane MCP server with Claude Code

Updated Files

  • docs/.vitepress/config.mts - Added new page to sidebar under "Build and extend Plane"

Documentation Contents

The new guide includes:

1. Three Setup Methods

  • OAuth Authentication - For Plane Cloud users with copy-paste command
  • Personal Access Token - For CI/CD environments
  • Local Stdio - For self-hosted Plane instances

2. Configuration Options

  • Scope options (--scope local, project, user) to control config storage location
  • Verification steps using claude mcp list, claude mcp get, and /mcp

3. Available Tools Reference

Complete table of 55+ tools organized across 8 categories:

  • Projects (5 tools)
  • Work Items (9 tools)
  • Cycles (8 tools)
  • Modules (7 tools)
  • Initiatives (5 tools)
  • Intake (6 tools)
  • Properties (6 tools)
  • Users (5 tools)

4. Practical Examples

8 real-world scenarios showing:

  • Natural language prompts users would write
  • Which MCP tools Claude Code invokes
  • Expected results

Examples cover:

  • Listing projects
  • Creating work items
  • Searching with filters
  • Planning cycles
  • Triaging intake
  • Getting project overviews
  • Creating and populating modules
  • Transferring items between cycles

5. Troubleshooting Guide

Common issues and solutions:

  • Debug logging
  • Auth token reset
  • Timeout configuration
  • Runtime health checks

Testing

  • Documentation renders correctly in VitePress
  • All code blocks are properly formatted
  • Sidebar navigation includes new page
  • All internal links work
  • Commands are copy-paste ready

Screenshots

Add screenshots of the rendered documentation if available

Related

  • Closes #[issue-number] (if applicable)
  • Related to MCP server implementation
  • Part of developer tools documentation initiative

Summary by CodeRabbit

  • Documentation
    • Added comprehensive guide for MCP Server integration with Claude Code, covering setup methods, authentication, environment variables, available tools, verification steps, usage examples, server management, and troubleshooting.
    • Updated site navigation to include the new "MCP Server for Claude Code" entry under Dev Tools.

@vercel
Copy link

vercel bot commented Feb 4, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
developer-docs Ready Ready Preview, Comment Feb 4, 2026 0:40am

Request Review

@coderabbitai
Copy link

coderabbitai bot commented Feb 4, 2026

📝 Walkthrough

Walkthrough

Adds a new docs page "MCP Server for Claude Code" and a navigation entry linking to it under the Dev Tools section in the site config.

Changes

Cohort / File(s) Summary
Navigation Configuration
docs/.vitepress/config.mts
Inserted a new navigation item "MCP Server for Claude Code" under the Dev Tools section, linking to /dev-tools/mcp-server-claude-code.
Documentation
docs/dev-tools/mcp-server-claude-code.md
Added a comprehensive documentation page describing MCP Server integration with Claude Code: prerequisites, setup methods (HTTP OAuth, HTTP PAT, Local stdio), env vars, verification, available tools, examples, server management, and troubleshooting.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐰 I hop to a doc, fresh and bright,
Claude Code and MCP meet in light,
Setup, tools, and a troubleshooting nudge,
A rabbit-approved guide—soft and smudge! 🥕📘

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The PR title accurately summarizes the main change: adding documentation for Claude Code MCP integration. It is concise, clear, and directly reflects the primary objective.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch feat-add-mcp-claude-code-guide

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In `@docs/dev-tools/mcp-server-claude-code.md`:
- Around line 139-211: The fenced prompt code blocks in
docs/dev-tools/mcp-server-claude-code.md lack language identifiers which
triggers markdownlint MD040; fix by updating each prompt fence (the opening ```
lines for blocks containing prompts like "List all projects in my workspace.",
"Create a bug in project WEB titled ...", "Search for work items related to
...", etc.) to include a language tag such as text (change ``` to ```text) so
every fenced prompt block has an explicit language identifier.

Comment on lines 139 to 211
**Prompt:**
```
List all projects in my workspace.
```

Claude Code calls `list_projects` and returns a summary of all projects including their identifiers, lead, and status.

### Create a work item

**Prompt:**
```
Create a bug in project WEB titled "Fix login redirect loop" and assign it to me.
```

Claude Code calls `get_me` to find your user ID, then `create_work_item` with the project ID, name, and assignee.

### Search across work items

**Prompt:**
```
Search for work items related to "authentication" across the workspace.
```

Claude Code calls `search_work_items` with the query string and returns matching results from all projects.

### Plan a cycle

**Prompt:**
```
Create a new cycle called "Sprint 24" in project WEB starting today and
ending in 2 weeks. Add work items WEB-102, WEB-115, and WEB-118 to it.
```

Claude Code calls `create_cycle` with the name and dates, then `add_work_items_to_cycle` to attach the specified items.

### Triage intake items

**Prompt:**
```
Show me all intake items in project MOBILE and accept the ones related to
crash reports.
```

Claude Code calls `list_intake_work_items` to retrieve pending items, then `update_intake_work_item` to accept the relevant ones.

### Get a project overview

**Prompt:**
```
Give me a summary of project BACKEND — what cycles are active, how many
open work items are there, and who are the members?
```

Claude Code calls `retrieve_project`, `list_cycles`, `list_work_items`, and `get_project_members` to assemble a full overview.

### Manage modules

**Prompt:**
```
Create a module called "Auth Revamp" in project WEB and add all work items
tagged with the "auth" label to it.
```

Claude Code calls `create_module`, then `list_work_items` with label filtering, and finally `add_work_items_to_module` to associate the items.

### Move work items between cycles

**Prompt:**
```
Transfer all incomplete work items from "Sprint 23" to "Sprint 24" in
project WEB.
```

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Add language identifiers to fenced prompt blocks (MD040).

markdownlint flags these prompt fences; use a language like text to keep lint clean.

💡 Suggested fix
-```
+```text
 List all projects in my workspace.

@@
- +text
Create a bug in project WEB titled "Fix login redirect loop" and assign it to me.

@@
-```
+```text
Search for work items related to "authentication" across the workspace.

@@
- +text
Create a new cycle called "Sprint 24" in project WEB starting today and
ending in 2 weeks. Add work items WEB-102, WEB-115, and WEB-118 to it.

@@
-```
+```text
Show me all intake items in project MOBILE and accept the ones related to
crash reports.

@@
- +text
Give me a summary of project BACKEND — what cycles are active, how many
open work items are there, and who are the members?

@@
-```
+```text
Create a module called "Auth Revamp" in project WEB and add all work items
tagged with the "auth" label to it.

@@
- +text
Transfer all incomplete work items from "Sprint 23" to "Sprint 24" in
project WEB.

🧰 Tools
🪛 markdownlint-cli2 (0.20.0)

[warning] 140-140: Fenced code blocks should have a language specified

(MD040, fenced-code-language)


[warning] 149-149: Fenced code blocks should have a language specified

(MD040, fenced-code-language)


[warning] 158-158: Fenced code blocks should have a language specified

(MD040, fenced-code-language)


[warning] 167-167: Fenced code blocks should have a language specified

(MD040, fenced-code-language)


[warning] 177-177: Fenced code blocks should have a language specified

(MD040, fenced-code-language)


[warning] 187-187: Fenced code blocks should have a language specified

(MD040, fenced-code-language)


[warning] 197-197: Fenced code blocks should have a language specified

(MD040, fenced-code-language)


[warning] 207-207: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

🤖 Prompt for AI Agents
In `@docs/dev-tools/mcp-server-claude-code.md` around lines 139 - 211, The fenced
prompt code blocks in docs/dev-tools/mcp-server-claude-code.md lack language
identifiers which triggers markdownlint MD040; fix by updating each prompt fence
(the opening ``` lines for blocks containing prompts like "List all projects in
my workspace.", "Create a bug in project WEB titled ...", "Search for work items
related to ...", etc.) to include a language tag such as text (change ``` to
```text) so every fenced prompt block has an explicit language identifier.

@Prashant-Surya
Copy link
Member

@sriramveeraghanta any reason you create a new page instead of adding this in existing MCP server page?

@sriramveeraghanta
Copy link
Member Author

I wanted to keep it separate for SEO.

@sriramveeraghanta sriramveeraghanta merged commit 889df68 into master Feb 5, 2026
3 checks passed
@sriramveeraghanta sriramveeraghanta deleted the feat-add-mcp-claude-code-guide branch February 5, 2026 10:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants