linear-notion-mix

My perfect blend of Notion and Linear APIs for my work.

This MCP server was generated using the Template Orchestrator and includes the following integrations:

Available Tools

This MCP server provides 43 tools across 2 integrations:

Linear Tools

• linear_get_team: Get team details including members and settings
• linear_get_user: Get user details and profile information
• linear_get_issue: Retrieve issue details by ID or identifier
• linear_get_viewer: Get current user information (viewer)
• linear_list_teams: List all teams in the workspace using simplified query structure. Removed problematic fields (timezone, private, archivedAt, members) to resolve 400 Bad Request errors. Returns core team identification data (id, name, key).
• linear_list_users: List all users in the workspace
• linear_get_project: Get project details including associated issues
• linear_list_issues: List issues with optional filtering by team, state, assignee, and labels
• linear_list_labels: List all labels available in the workspace
• linear_apply_labels: Apply labels to an issue
• linear_assign_issue: Assign a user to an issue
• linear_create_issue: Create a new issue with title, description, and team assignment
• linear_create_label: Create a new label for issue categorization
• linear_delete_issue: Delete an issue by ID
• linear_update_issue: Update issue properties including title, description, priority, and state
• linear_list_comments: List comments for an issue
• linear_list_projects: List all projects with optional filtering
• linear_search_issues: Search issues using filters (replaces deprecated issueSearch endpoint). Migrated from deprecated 'issueSearch' to current 'issues' endpoint with filtering. Use filter objects instead of text queries for more flexible and powerful search capabilities.
• linear_create_comment: Create a comment on an issue
• linear_create_project: Create a new project
• linear_update_project: Update project properties
• linear_transition_issue: Transition an issue to a different workflow state
• linear_list_workflow_states: List all workflow states available in the workspace

Notion Tools

• notion_get_me: Get current bot user
• notion_search: Search pages and databases
• notion_get_page: Get page by ID
• notion_get_user: Get user by ID
• notion_get_block: Get block by ID
• notion_list_users: List all users
• notion_create_page: Create a new page. Note: Creating pages directly in workspace root requires special permissions - use database or page parents instead.
• notion_update_page: Update page properties
• notion_delete_block: Delete a block
• notion_get_comments: Get comments for a page or block
• notion_get_database: Get database by ID
• notion_update_block: Update block content
• notion_create_comment: Create a comment on a page or block
• notion_list_databases: ⚠️ DEPRECATED: This endpoint is deprecated by Notion API. Use the search endpoint with database filter instead.
• notion_query_database: Query database pages
• notion_create_database: Create a new database
• notion_update_database: Update database properties
• notion_get_page_property: Get page property by ID
• notion_get_block_children: Get block children
• notion_append_block_children: Append blocks to a parent block

Installation

npm install @coretext-ai/linear-notion-mix-5fb1ea3c-89de-46d8-875b-cd3b49dc7e62

Environment Setup

Create a .env file with the following variables:

LINEAR_API_KEY=your_linear_api_key_here
NOTION_ACCESS_TOKEN=your_notion_access_token_here

Usage

Running the server

# Development mode
npm run dev

# Production mode
npm run build && npm start

Using with Claude Desktop

Add this to your Claude Desktop configuration:

{
  "mcpServers": {
    "linear-notion-mix": {
      "command": "npx",
      "args": ["@coretext-ai/linear-notion-mix-5fb1ea3c-89de-46d8-875b-cd3b49dc7e62"],
      "env": {
        "LINEAR_API_KEY": "your_linear_api_key_here",
        "NOTION_ACCESS_TOKEN": "your_notion_access_token_here"
      }
    }
  }
}

Instructions for Fetching API Keys/Tokens

• COMING SOON

Advanced Features

Request Cancellation

This MCP server supports request cancellation according to the MCP cancellation specification. Clients can cancel in-progress requests by sending a notifications/cancelled message with the request ID.

When a request is cancelled:

• The server immediately stops processing the request
• Any ongoing API calls are aborted
• Resources are cleaned up
• No response is sent for the cancelled request

Progress Notifications

The server supports progress notifications for long-running operations according to the MCP progress specification.

To receive progress updates:

1. Include a progressToken in your request metadata
2. The server will send notifications/progress messages with:
   • Current progress value
   • Total value (when known)
   • Human-readable status messages

Progress is reported for:

• Multi-step operations
• Batch processing
• Long-running API calls
• File uploads/downloads

Example progress notification:

{
  "method": "notifications/progress",
  "params": {
    "progressToken": "operation-123",
    "progress": 45,
    "total": 100,
    "message": "Processing item 45 of 100..."
  }
}

Generated Information

• Generated at: Mon Nov 03 2025 16:33:31 GMT+0000 (Coordinated Universal Time)
• Orchestrator version: 0.0.2
• Template repository: Coretext-AI-Dev/server-template-v2
• Total endpoints: 43