Skip to main content
Glama
aiproject-mcp
by evrenonur

AIProject MCP Server

This MCP server wraps the AIProject project/task API described in api.md.

Run

npm install
npm run build
npm start

Use aiproject-mcp as a stdio MCP server after build.

Related MCP server: Context Apps

MCP Config

Local build:

{
  "mcpServers": {
    "aiproject": {
      "command": "C:\\ServBay\\bin\\node.cmd",
      "args": [
        "C:\\Users\\Onur\\Desktop\\mcp\\dist\\src\\index.js"
      ],
      "env": {
        "AIPROJECT_BASE_URL": "http://127.0.0.1:8000/",
        "AIPROJECT_API_KEY": "<API_KEY>"
      }
    }
  }
}

After npm publish:

{
  "mcpServers": {
    "aiproject": {
      "command": "npx",
      "args": [
        "-y",
        "aiproject-mcp"
      ],
      "env": {
        "AIPROJECT_BASE_URL": "http://127.0.0.1:8000/",
        "AIPROJECT_API_KEY": "<API_KEY>"
      }
    }
  }
}

Credentials

The server reads credentials from environment variables:

  • AIPROJECT_BASE_URL: API root or app root. Both http://127.0.0.1:8000 and http://127.0.0.1:8000/api/v1 are accepted. If the app root is supplied, /api/v1 is appended automatically.

  • AIPROJECT_API_KEY: API key sent as X-API-Key.

Every MCP tool also accepts optional credential overrides in its input:

  • baseUrl: Override AIPROJECT_BASE_URL for one call.

  • apiKey: Override AIPROJECT_API_KEY for one call.

Tools

  • aiproject_get_me: GET /me; verify the API key and return the current user.

  • aiproject_list_projects: GET /projects; paginated project summaries.

  • aiproject_create_project: POST /projects; create a project with name, github_url, clickup_url.

  • aiproject_get_project: GET /projects/{project}; get one project.

  • aiproject_update_project: PUT /projects/{project}; full project update, all project fields required.

  • aiproject_delete_project: DELETE /projects/{project}; deletes the project and its tasks.

  • aiproject_list_tasks: GET /projects/{project}/tasks; paginated task summaries. Does not return content.

  • aiproject_create_task: POST /projects/{project}/tasks; create a task with long content and assignments. Returns summary without content.

  • aiproject_get_task: GET /projects/{project}/tasks/{task}; the only task read tool that returns long content.

  • aiproject_update_task: PUT /projects/{project}/tasks/{task}; full task update. The sent assignments replace the old list. Returns summary without content.

  • aiproject_delete_task: DELETE /projects/{project}/tasks/{task}; deletes the task and assignments.

  • aiproject_update_assignment_status: PATCH /projects/{project}/tasks/{task}/assignments/{type}; update one existing team status. It does not create missing assignments.

Usage Guidance

List tasks first with aiproject_list_tasks because it returns lightweight summaries. Call aiproject_get_task only for the specific task whose long content must be read.

Use aiproject_update_assignment_status when only one team's status changes. Use aiproject_update_task when the title, content, or assignment team list changes.

Test

npm test

By default, the integration test calls http://127.0.0.1:8000/api/v1/me through MCP with a dummy API key and expects the documented 401 auth response. To test with a real key:

$env:AIPROJECT_BASE_URL = "http://127.0.0.1:8000/"
$env:AIPROJECT_API_KEY = "<API_KEY>"
npm test

Available Tools

12 tools
aiproject_create_projectCreate ProjectC

Calls POST /projects to create a project. Required fields are name, github_url, and clickup_url.

Inputs: name (required), github_url (required), clickup_url (required), baseUrl, +1 more.

aiproject_create_taskCreate Project TaskA

Calls POST /projects/{project}/tasks to create a task with full content and one or more assignments. The API response is a task summary and intentionally omits content.

Inputs: project (required), title (required), content (required), assignments (required), +2 more.

aiproject_delete_projectDelete ProjectA
Destructive

Calls DELETE /projects/{project}. This also deletes the project's tasks and task assignments. Use only when the user explicitly wants project deletion.

Inputs: project (required), baseUrl, apiKey.

aiproject_delete_taskDelete Project TaskA
Destructive

Calls DELETE /projects/{project}/tasks/{task}. This also deletes the task's assignment records. Use only when the user explicitly wants task deletion.

Inputs: project (required), task (required), baseUrl, apiKey.

aiproject_get_meGet Current API UserA
Read-onlyIdempotent

Calls GET /me to verify the supplied apiKey and return the user it belongs to. Use this first when checking credentials or identifying the current API user.

Inputs: baseUrl, apiKey.

aiproject_get_projectGet ProjectA
Read-onlyIdempotent

Calls GET /projects/{project}. Use this when a single project's metadata is needed.

Inputs: project (required), baseUrl, apiKey.

aiproject_get_taskGet Task DetailA
Read-onlyIdempotent

Calls GET /projects/{project}/tasks/{task}. This is the only task read endpoint that returns the long content field. Use it only after selecting a specific task from a summary list.

Inputs: project (required), task (required), baseUrl, apiKey.

aiproject_list_projectsList ProjectsA
Read-onlyIdempotent

Calls GET /projects and returns a paginated lightweight project list with tasks_count. Use this before selecting a project ID for task operations.

Inputs: baseUrl, apiKey, page, per_page.

aiproject_list_tasksList Project TasksA
Read-onlyIdempotent

Calls GET /projects/{project}/tasks and returns paginated task summaries only. It never returns long content. Use this to scan tasks and optionally filter by assignment type/status before calling aiproject_get_task for one selected task.

Inputs: project (required), baseUrl, apiKey, page, +3 more.

aiproject_update_assignment_statusUpdate Task Assignment StatusA

Calls PATCH /projects/{project}/tasks/{task}/assignments/{type} to update one existing team's status. It does not create a missing assignment; if the task does not already have that type, the API returns 404. Use PUT aiproject_update_task to add or remove teams. The response is a task summary without content.

Inputs: project (required), task (required), type (required), status (required), +2 more.

aiproject_update_projectUpdate ProjectA

Calls PUT /projects/{project}. This is a full project update, so send name, github_url, and clickup_url together.

Inputs: project (required), name (required), github_url (required), clickup_url (required), +2 more.

aiproject_update_taskUpdate Project TaskA

Calls PUT /projects/{project}/tasks/{task}. This is a full task update: title, content, and the complete new assignments list must be sent. Assignments omitted from the list are removed by the API. The response is a task summary without content.

Inputs: project (required), task (required), title (required), content (required), +3 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool targets a distinct operation on projects, tasks, or user info, with clear separation of concerns. No two tools have overlapping purposes.

    Naming Consistency5/5

    All tools follow the consistent verb_noun pattern with snake_case, prefixed by 'aiproject_', making the naming predictable and easy to parse.

    Tool Count5/5

    12 tools is an appropriate scope for a project/task management server, covering CRUD for two main entities plus user and assignment status operations.

    Completeness4/5

    Core CRUD lifecycle for projects and tasks is complete. Minor gap: no dedicated assignment creation tool, but assignments are managed through task creation/update, so it's a minor weakness.

    Related MCP Connectors

    Related MCP Servers