S08-E01

This MCP server bridges your Plane project with MCP tooling. It reads configuration from appsettings.json and uses Plane's API key to access your Plane project data. Once running, you can connect to the MCP Inspector to verify it is registered and exposed as a tool. In the MCP Inspector UI, connect to the server, list available tools, and execute get_all_work_item_statuses to retrieve the standard Plane work item statuses. The server is designed to be compatible with MCP clients that expect a dotnet-based server exposing Plane-related data via the MCP protocol.

Prerequisites:

• .NET 6.0+ SDK or newer
• Git

Installation steps:

1. Clone the repository: git clone https://github.com/binarythistle/S08-E01-MCP-Server.git
2. Change into the project directory: cd S08-E01-MCP-Server
3. Restore dependencies: dotnet restore
4. Configure environment and settings:
   • Open appsettings.json and set Plane API details: { "PlaneAPIKey": "<your-key>", "BaseUrl": "https://plane.so/", "Workspace": "<your-workspace>", "ProjectId": "<your-project-id>" }
5. Run the server: dotnet run --project S08-E01-MCP-Server/S08-E01-MCP-Server.csproj
6. Optional: register with an MCP client inspector as described in the README, using: npx @modelcontextprotocol/inspector dotnet run

Notes:

• Ensure your Plane API key is kept secret; use user secrets or environment variables in production.
• The appsettings.json values must reflect your actual Plane project configuration.
• If the server fails to connect to Plane, check network access and API key validity.
• To integrate with MCP tools, you can use MCP Inspector to browse and run tools such as get_all_work_item_statuses; ensure Node.js is installed for the Inspector client UI.
• This server exposes a dotnet-based endpoint compatible with MCP tooling; no npm package is required.