Repository navigation
Add cohesivity plugin - #12
Open
shouryamaanjain wants to merge 1 commit into
Open
shouryamaanjain wants to merge 1 commit into
shouryamaanjain wants to merge 1 commit into
Conversation
This branch has not been deployed
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.
Adds a
cohesivityplugin: an MCP server and a skill that let ECA set up a backend for the app it is building.When a user asks ECA to build something that needs a database or a deploy, the agent usually has to stop and ask them to create accounts and paste keys. Cohesivity is a hosted MCP server that provisions Postgres, Redis, object storage, hosting and auth without an account.
create_tenantreturns a temporary project that lasts 72 hours, and the user can claim it to keep it.What is in it:
.mcp.json: the hosted server athttps://cohesivity.ai/mcp. Only a URL; it needs no key and never asks for OAuth.skills/cohesivity/SKILL.md: when to reach for it, reusing the project's.cohesivityfile instead of creating a second project, reading a service's docs before provisioning it, keeping keys out of client code and commits, and asking before claiming.README.md, and an entry inmarketplace.jsonunder Development.Why a plugin and not only the MCP config: the config on its own is going into the ECA docs (editor-code-assistant/eca#651). Without the skill, though, the agent sees six tools and nothing about reusing a project, where the credentials should go, or when to ask the user. The plugin ships both and installs with
/plugin-install cohesivity.How I checked it: I ran the ECA 0.165.0 release binary with this repo as a local plugin source and
install: ["cohesivity"]. The plugin loaded, the MCP server came up with its six tools, and the skill appeared in the system prompt's skill list. A chat driven by a scripted OpenAI-compatible provider then loaded the skill witheca__skill, calledcohesivity__create_tenantandcohesivity__provision_resource, and got a Postgres database on the live server.npm run buildinwebsite/renders the plugin page. The new entry validates againstmarketplace.schema.json; the file as a whole fails that schema only on the existingBDDtag in the allium entry, which this PR leaves alone. I have not run it with a real model.Disclosure: I work at Cohesivity, which operates this MCP server.