linear
Server Details
Search, read and create Linear issues, projects, teams and cycles.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
8 toolslinear_add_commentAdd comment (WRITE — mutates Linear)Inspect
⚠️ WRITE / MUTATING: posts a comment on an issue. Requires the issueId (UUID) and a markdown body. GraphQL: mutation commentCreate.
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | Comment text in markdown. | |
| issueId | Yes | UUID of the issue to comment on (the `id` field, not the ENG-123 identifier). |
linear_create_issueCreate issue (WRITE — mutates Linear)Inspect
⚠️ WRITE / MUTATING: creates a new issue in Linear. Requires a teamId (from linear_list_teams) and a title. Optional description (markdown), priority (0=none,1=urgent,2=high,3=medium,4=low), and assigneeId. GraphQL: mutation issueCreate.
| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes | Issue title. | |
| teamId | Yes | UUID of the team to create the issue in (from linear_list_teams). | |
| priority | No | 0 none, 1 urgent, 2 high, 3 medium, 4 low. | |
| assigneeId | No | UUID of the user to assign the issue to. | |
| description | No | Issue body in markdown. |
linear_get_issueGet one issueInspect
Fetch a single issue by its UUID or human identifier (e.g. "ENG-123"), including description, state, assignee and recent comments. Read-only. GraphQL: query issue(id).
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Issue UUID or identifier like "ENG-123". |
linear_list_cyclesList cyclesInspect
List cycles (sprints), optionally scoped to a team by key, with number, name and start/end dates. Read-only. GraphQL: query cycles(filter).
| Name | Required | Description | Default |
|---|---|---|---|
| first | No | Max cycles to return. Default 25. | |
| teamKey | No | Team key, e.g. "ENG", to scope cycles to one team. |
linear_list_projectsList projectsInspect
List projects in the workspace (id, name, state, progress, target date). Read-only. GraphQL: query projects.
| Name | Required | Description | Default |
|---|---|---|---|
| first | No | Max projects to return. Default 50. |
linear_list_teamsList teamsInspect
List the teams in the workspace (id, key, name). Use a team's id for linear_create_issue or its key for linear_search_issues. Read-only. GraphQL: query teams.
| Name | Required | Description | Default |
|---|---|---|---|
| first | No | Max teams to return. Default 50. |
linear_my_issuesMy assigned issuesInspect
List issues assigned to the current user (the API key's owner / OAuth actor) via viewer.assignedIssues. Read-only. GraphQL: query viewer { assignedIssues }.
| Name | Required | Description | Default |
|---|---|---|---|
| first | No | Max issues to return. Default 25. |
linear_search_issuesSearch / filter issuesInspect
Find issues, optionally filtered by a text query (matches title), team key, workflow-state name, or assignee email. Read-only. GraphQL: query issues(filter, first).
| Name | Required | Description | Default |
|---|---|---|---|
| first | No | Max issues to return. Default 25. | |
| query | No | Free text to match against issue titles (containsIgnoreCase). | |
| state | No | Workflow-state name, e.g. "In Progress", "Todo", "Done". | |
| teamKey | No | Team key, e.g. "ENG". Filters to that team. | |
| assigneeEmail | No | Filter to issues assigned to this user email. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!