Speakeasy Logo
Skip to Content
Gram DocumentationExamplesCreating an MCP server for Taskmaster

Creating an MCP server for Taskmaster

This guide walks you through creating a Gram-hosted MCP server for Taskmaster. You’ll learn how to upload an OpenAPI document, create a toolset, configure authentication, and publish your MCP server.

Taskmaster showcase

What is Taskmaster?

:::note[Try it out] You can try out Taskmaster here . :::

Taskmaster is a full-stack CRUD application for tasks and projects. It includes:

  • A web UI for managing projects and tasks
  • A built-in HTTP API
  • OAuth 2.0 authentication
  • A Neon PostgreSQL database for storing tasks and projects

This guide focuses on using Taskmaster to manage tasks and projects via an MCP server, although you can also manage them using the web UI or the built-in HTTP API.

Find the full code and OpenAPI document in the Taskmaster repository .

Prerequisites

To follow this tutorial, you need:

Setting up a Gram project

In the Gram dashboard , click New Project to start the guided setup flow for creating a toolset and MCP server.

Screenshot of the Gram dashboard showing the New Project link

Enter a project name and click Submit.

Gram will then guide you through the following steps:

1. Upload the OpenAPI document

Upload the Taskmaster OpenAPI document , enter the name of your API, and click Continue.

Screenshot of the upload your OpenAPI spec dialog

2. Create a toolset

Give your toolset a name (for example, Taskmaster) and click Continue.

Screenshot of the create toolset dialog

Notice that this dialog also displays the names of the tools generated from your OpenAPI document.

3. Configure MCP

Enter a URL slug for the MCP server and click Continue.

Screenshot of the configure MCP dialog

Gram then creates the toolset from the OpenAPI document.

Click Toolsets in the sidebar to view the Taskmaster toolset.

Screenshot of the Gram dashboard showing the Taskmaster toolset

As you can see, the toolset needs environment variables before you can use it.

Getting a Taskmaster API key

Before configuring environment variables, create an API key:

  • Navigate to your Taskmaster app (for example, https://taskmaster-ritza.vercel.app).
  • Sign in and go to Settings → Developer.
  • Under API Keys, click New Key.
  • Give it a label and click Create.
  • Copy the API key. You will not be able to see it again.

Configuring environment variables

Environments store API keys and configuration separately from your toolset logic.

In the Environments tab, click the Default environment. Click the three-dot menu in the top-right corner of the environment card, and in the dropdown, click Fill for Toolset. Select the Taskmaster toolset and click Fill Variables to automatically populate the required variables.

Screenshot showing the fill for toolset dialog to automatically populate required variables

Configure the following environment variables:

  • Set the TASKMASTER_SERVER_URL environment variable to your API base URL. For example: https://taskmaster-ritza.vercel.app/api
  • Set the TASKMASTER_ACCESS_TOKEN environment variable to your API key. For example: tm_abc123_def456 Alternatively, you can set an X-API-Key header to the same value. The API accepts both.

Click Update and then Save.

Set server URL

Publishing an MCP server

Let’s make the toolset available as an MCP server.

Go to the MCP tab, find the Taskmaster toolset, and click on it to open the MCP details page.

Scroll down to the Visibility section and tick the Public checkbox.

Screenshot of the MCP details page

Next, you’ll need to copy the MCP server configuration.

Scroll down to the MCP Config section and copy the Public Server configuration.

Screenshot showing the MCP server config dialog for the Taskmaster toolset

The configuration looks something like this:

Use the Authenticated Server configuration if you want to use the MCP server in a private environment.

You need an API key to use an authenticated server. Generate an API key in the Taskmaster Settings → Developer → API Keys page, copy it, and paste it in the GRAM_KEY environment variable in place of <your-key-here>.

The authenticated server configuration looks something like this:

Testing the MCP server

Before connecting to external clients, test your setup by using the Gram Playground to verify that your tools are working correctly.

What’s next

Your Taskmaster MCP server is now ready to use with any MCP client. You can connect it to:

Last updated on