S08 E01

v1.0.0Developer Toolsstable

This is the companion code for Season 8 Episode 1

s08-e01-mcp-servermcpai-integration
Share:
9
Stars
0
Downloads
0
Weekly
0/5

What is S08 E01?

S08 E01 is a Model Context Protocol (MCP) server that allows AI assistants like Claude, Cursor, and VS Code to this is the companion code for season 8 episode 1

This is the companion code for Season 8 Episode 1

This server falls under the Developer Tools category on MCPgee, the world's largest MCP server directory with 33,000+ servers.

Features

  • This is the companion code for Season 8 Episode 1

Use Cases

Companion code implementation for Season 8 Episode 1 demonstrations.
binarythistle

Maintainer

LicenseMIT
Languagec#
Versionv1.0.0
UpdatedApr 16, 2026
Statushealthy
Maintenanceactive

Works with

ClaudeOpenAIwindowsmacoslinux

Installation

Manual Installation

npx s08-e01-mcp-server

Configuration

Configuration Details

Config File

claude_desktop_config.json

Performance

Response Metrics

Response Time< 200ms
ThroughputMedium

Resource Usage

Memory UsageLow
CPU UsageLow

How to Set Up and Use S08 E01

The S08-E01 MCP Server is a .NET/C# companion code project for Season 8 Episode 1 of the BinaryThistle tutorial series. It demonstrates how to build a Model Context Protocol server in C# that integrates with the Plane project management tool, exposing work item status retrieval as an MCP tool consumable by Claude Desktop and the MCP Inspector.

Prerequisites

  • .NET 8 SDK or later installed (verify with: dotnet --version)
  • Node.js 18+ for the MCP Inspector (npx @modelcontextprotocol/inspector)
  • Active Plane.so account with a workspace and project
  • Plane API key from https://app.plane.so/profile/api-tokens
  • Visual Studio Code or another C# IDE (optional but recommended)
1

Clone the repository

Clone the S08-E01 MCP Server repository and open it in your editor.

git clone https://github.com/binarythistle/S08-E01-MCP-Server.git
cd S08-E01-MCP-Server
code .
2

Configure appsettings.json

Open appsettings.json and fill in your Plane workspace slug, project ID, and base URL. These values are visible in the URL when you navigate to your project in Plane.

{
  "PlaneSettings": {
    "BaseUrl": "https://api.plane.so/api/v1",
    "Workspace": "your-workspace-slug",
    "ProjectId": "your-project-uuid"
  }
}
3

Set your Plane API key as a user secret

Store the Plane API key securely using .NET user secrets so it is never committed to source control.

dotnet user-secrets set "PlaneAPIKey" "your_plane_api_key_here"
4

Run with the MCP Inspector

Launch the server and connect to it using the MCP Inspector for interactive testing. The Inspector allows you to list and call tools without needing Claude Desktop.

npx @modelcontextprotocol/inspector dotnet run
5

Connect and test tools

In the MCP Inspector browser UI, click Connect, then List Tools to see the available tools. Select 'get_all_work_item_statuses' and click Run Tool to retrieve your Plane project's work item statuses.

S08 E01 Examples

Client configuration

To connect to Claude Desktop, build the project first and reference the built binary. Ensure PlaneAPIKey is available as an environment variable or via user secrets.

{
  "mcpServers": {
    "plane-mcp": {
      "command": "dotnet",
      "args": ["run", "--project", "/absolute/path/to/S08-E01-MCP-Server"],
      "env": {
        "PlaneAPIKey": "your_plane_api_key_here"
      }
    }
  }
}

Prompts to try

Ask Claude these questions after connecting the Plane MCP server.

- "List all work item statuses in my Plane project"
- "What statuses are available for tracking issues in Plane?"
- "Show me the current workflow states for the project"

Troubleshooting S08 E01

dotnet user-secrets command fails

Ensure the project file has a <UserSecretsId> element. If missing, run 'dotnet user-secrets init' in the project directory first, then set the secret again.

MCP Inspector cannot connect to the server

Verify that 'dotnet run' builds and starts successfully without errors before connecting the Inspector. Check that appsettings.json has valid Plane workspace slug and project ID values — these are the slug in your Plane workspace URL, not the display name.

API errors when calling get_all_work_item_statuses

Confirm your Plane API key is valid by testing it with curl: 'curl -H "X-Api-Key: YOUR_KEY" https://api.plane.so/api/v1/workspaces/'. Ensure the ProjectId in appsettings.json is the UUID shown in the Plane project settings, not a display name.

Frequently Asked Questions about S08 E01

What is S08 E01?

S08 E01 is a Model Context Protocol (MCP) server that this is the companion code for season 8 episode 1 It connects AI assistants to external tools and data sources through a standardized interface.

How do I install S08 E01?

Follow the installation instructions on the S08 E01 GitHub repository. Clone the repo, install dependencies, and add the server config to your AI client.

Which AI clients work with S08 E01?

S08 E01 works with all major MCP-compatible AI clients including Claude Desktop, Claude Code, Cursor, VS Code (GitHub Copilot), Windsurf, and Cline.

Is S08 E01 free to use?

Yes, S08 E01 is open source and available under the MIT license. You can use it freely in both personal and commercial projects.

Browse More Developer Tools MCP Servers

Explore all developer tools servers available in the MCPgee directory. Each server includes setup guides for Claude, Cursor, and VS Code.

Quick Config Preview

{ "mcpServers": { "s08-e01-mcp-server": { "command": "npx", "args": ["-y", "s08-e01-mcp-server"] } } }

Add this to your claude_desktop_config.json or .cursor/mcp.json

Read the full setup guide →

Ready to use S08 E01?

Browse our complete directory of 33,000+ MCP servers, read setup guides for your editor, and start building with the Model Context Protocol.

33,000+ ServersFree & Open SourceStep-by-Step Guides