Skip to content

MCP server is difficult to use #3078

Description

@edmcman

Prerequisites

Please answer the following questions for yourself before submitting an issue.

  • I am running the latest version
  • I did read the README!
  • I checked the documentation and found no answer
  • I checked to make sure that this issue has not already been filed
  • I'm reporting the issue to the correct repository (for multi-repository projects)
  • I have read and checked all configs (with all optional parts)
  • Asked and no solution about my issue with deepwiki

Current Behavior

The MCP server is difficult to use. Most MCP servers can be run by a command-line tool like uvx or npx. In contrast, CAPE's MCP server requires you to:

  1. Clone the repository
  2. Edit the config to enable tools because they are off by default
  3. Install the prereqs using poetry

It would be nice if the MCP server was a separate entity that is perhaps listed on PyPI, and doesn't require a config other than an environment variable. I am happy to implement this if there is a consensus. (I will likely implement it regardless because the current procedure for clients is too heavyweight!)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions