mcpField
G
GitHub Actions for Plane-MCP

GitHub Actions for Plane-MCP

Local
github.com/CreodotVersion Control0Updated 81w ago
Repository

About GitHub Actions for Plane-MCP

GitHub Actions for Plane-MCP is a collection of GitHub Actions workflows for testing the project’s Plane API endpoints. It runs unit and integration tests on pushes, pull requests, scheduled runs, and manual requests.

Key features

  1. 01Tests Plane API endpoints
  2. 02Runs unit tests
  3. 03Runs integration tests and endpoint verification
  4. 04Supports scheduled and manual runs

Use cases

  1. 01Checking changes before merging
  2. 02Running daily endpoint checks
#open-source#typescript#plane#mcp#biomejs#modelcontextprotocol

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

GitHub Actions for Plane-MCP

This folder contains the GitHub Actions workflows configured for this project.

Secret Configuration

For integration tests to work correctly on GitHub Actions, you need to configure the following secrets in your GitHub repository settings:

  • TEST_PLANE_TOKEN_API: Your Plane.so API key for testing
  • TEST_PLANE_WORKSPACE_SLUG: Your Plane.so workspace slug (e.g., "your-organization")
How to Configure Secrets
  1. Go to your GitHub repository
  2. Navigate to "Settings" > "Secrets and variables" > "Actions"
  3. Click on "New repository secret"
  4. Add the two secrets mentioned above

Available Workflows

test-endpoints.yml

This workflow tests the Plane API endpoints. It is triggered in the following cases:

  • When pushing to main/master branches
  • When creating a pull request to main/master
  • Manually via the GitHub Actions interface
  • Automatically every day at midnight (00:00 UTC)

It runs two jobs:

  1. unit-tests: Runs all unit tests
  2. integration-tests: Runs integration tests and the endpoint verification script

Manual Execution

To manually run tests via GitHub Actions:

  1. Go to the "Actions" tab of your repository
  2. Select the "Test API Endpoints" workflow in the sidebar
  3. Click on "Run workflow"
  4. Choose the branch on which to run the tests
  5. Click on "Run workflow"

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.