MCP issue creation not working in self-hosted Community Edition

[Tanmaymundra]

I was able to set up the MCP environment using the provided configuration and can successfully retrieve the list of projects from the self-hosted version via MCP. However, I’m unable to create an issue under any project.

Is it possible that the MCP schema follows the commercial license structure, while the Community Edition uses a different schema ?
Or there seems to be issue with parameters definition while calling the api.

Claude Output

Unfortunately, even the read operation for issues is failing with the same error. It seems like only certain read operations work (get_projects, get_user, get_workspace_members), but anything that requires parameters is broken.
What works:

✅ get_projects (no parameters needed)
✅ get_user (no parameters needed)
✅ get_workspace_members (no parameters needed)

What doesn't work:

❌ list_project_issues (needs project_id)
❌ create_issue (needs project_id & issue_data)
❌ All other operations requiring parameters

The Planeso MCP server has a systematic issue with parameter validation. All tools that require input parameters are broken.

[Tanmaymundra]

Update

This started working locally after upgrading the Zod package. Something is breaking in that version, so the Zod package needs to be updated.

[gabrielrinaldi]

@Tanmaymundra the issue is that zod is not on the packages list, only on devdependencies, so npx will mix 3.x and 4.x when running. The solutions is to either change dev to 4.x or add zod to packages as 3.x. I am not a JS engineer, so I don't want to open a PR since I don't know the implications, but feel free to use my branch if you want. It is based on the branch that adds pages API.

[Prashant-Surya]

Closing this as we migrated entire mcp to fastmcp