Plugin · model context protocol

Groxbot + Devin MCP

AI-powered access to GitHub repository documentation and codebase analysis, including private repositories, via Devin.

How a Bot uses Devin MCP

4 Devin MCP tools. Connect under Plugins. The Bot still asks before anything leaves the thread.

  • Read the Devin MCP project you name. Reproduce, summarize, or draft a patch.
  • Never merge, deploy, or change production without approval.
  • End with steps, expected vs actual, and a minimal fixture when it can.

Never without you

  • Merge, deploy, or delete a repo
  • Change production config

First message

In Devin MCP, reproduce this bug. Steps, expected vs actual. Do not change production.

Tools a Bot can call

A sample from the Devin MCP toolkit. The Bot calls these after you connect. Writes that would go live still wait for approval.

  • Ask question
  • List available repos
  • Read wiki contents
  • Read wiki structure

Jobs that use Devin MCP

Related integrations

FAQ

Does Groxbot have a native Devin MCP integration?

Yes. Connect Devin MCP under Plugins. The Bot still asks before anything leaves the thread — sending engineering included.

Can a Bot change live Devin MCP data?

Not by default. Groxbot is talk-first: draft in the thread, grant access when it hits a wall. Live Devin MCP writes wait for you.

Do I need a workflow builder?

No. Create a Bot, message it, grant access as needed. There isn't anything to learn — it's like bringing on a coworker.