Repository navigation
feat(corsair): PM and CRM skill, and an MCP config Claude's directory accepts - #10
Merged
Merged
Conversation
… accepts Claude's plugin directory now refuses config fields Claude Code doesn't read unless the publisher is a Verified organization; it refused 0.1.5 for that. The Agent Plugins mcp.json needs $schema and type streamable-http, which the directory rejects, so the Claude manifests now declare their servers inline with type http and leave mcp.json to the other clients. Adds a corsair-workspace skill for Corsair's own PM and CRM (actions, lookups, an example script for each), mentions them in corsair-data and corsair-connect-apps, and bumps corsair to 0.1.6 and corsair-sdk to 0.1.2.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Claude's plugin directory refused corsair 0.1.5 (3cf3f59): "Config file fields outside the allowed list accepted only from Verified organizations." The same files passed its checks on Nov 4; the directory started applying the rule after that. It accepts a remote MCP server entry only with
typehttporsse, and no field Claude Code doesn't read. Ourmcp.jsonhas a top-level$schemaand"type": "streamable-http", and the Agent Plugins schema our CI checks requires both. So the two can't share that file.What changed
Claude gets its own MCP config. Both
.claude-plugin/plugin.jsonfiles now declare their server inline:and
corsair-docsthe same way for corsair-sdk. Claude Code no longer readsmcp.json, which stays as it was for Codex, Cursor and the Agent Plugins schema.scripts/check.mjsnow checks that each inline server matchesmcp.json(same name, typehttp, same URL) instead of requiring"./mcp.json".PM and CRM in the skills. A new
corsair-workspaceskill covers Corsair's own PM (teams, states, issues, projects, labels) and CRM (people, companies, deals, notes, tasks): the action names, the lookups to do first, and one example script each. Its examples ran against the ChatGPT review account today.corsair-dataandcorsair-connect-appsnow mention PM and CRM and keep their Slack, Gmail and GitHub examples. The READMEs and the plugin description lead with PM and CRM.Versions. corsair 0.1.6 (all four manifests and the marketplaces), corsair-sdk 0.1.2.
Evidence
claude plugin validate plugins/corsair,plugins/corsair-sdkand.: all pass.node scripts/check.mjs:ok: 2 plugins, 7 skills.mcp.jsonfiles are unchanged, so the CI schema check on them still applies as before.After merge: press "Check for new commits" on the directory submission. If it still refuses, the next suspect is
mcp.jsonsitting in the plugin folder at all.