This plugin helps Codex work with Devfolio through the Devfolio MCP server. It supports hackathon project submissions, profile side projects, active hackathon discovery, track/prize lookup, and upload URL generation.

Add the Devfolio plugin marketplace:

codex plugin marketplace add devfolioco/codex-plugin

Then open the Codex Plugins screen, choose Devfolio, and install the plugin.

It bundles:

• A devfolio skill for preparing and safely managing project submissions through Devfolio MCP.
• ./.mcp.json pointing Codex at the hosted Devfolio Streamable HTTP MCP server.
• MCP workflow guidance for Devfolio project and submission tools.

The plugin declares this MCP server:

{
  "mcpServers": {
    "devfolio": {
      "type": "http",
      "url": "https://mcp.devfolio.co/mcp"
    }
  }
}

Connect Devfolio MCP with the bare MCP URL:

codex mcp add devfolio \
  --url "https://mcp.devfolio.co/mcp"

Devfolio MCP uses OAuth. Codex should open a Devfolio consent screen during setup, where you can authorize Codex to read your Devfolio identity, profile, hackathon participation, and projects, plus manage projects when you ask Codex to create or update them.

After authorizing, start a new Codex thread and invoke the plugin:

@devfolio show my active hackathons

If Codex says an MCP server named devfolio already exists, remove the existing entry and add it again:

codex mcp remove devfolio
codex mcp add devfolio \
  --url "https://mcp.devfolio.co/mcp"

For staging, internal testers can use the same shape with the Devrel endpoint:

codex mcp add devfolio \
  --url "https://mcp.devrel.in/mcp"

Legacy MCP URLs with apiKey query parameters are no longer valid for production. Remove the key from any existing Devfolio MCP config and reconnect with the bare MCP URL.

1. Install the plugin from the Devfolio marketplace.
2. Connect the hosted MCP server with codex mcp add devfolio --url "https://mcp.devfolio.co/mcp".
3. Complete the Devfolio consent screen when Codex opens it.
4. Start a new Codex thread and use @devfolio.

The OAuth connection lets Codex call Devfolio MCP tools on your behalf. The plugin still requires explicit confirmation before create, update, upload, or publish actions.

Devfolio project publishing can make a project public immediately. The skill instructs Codex to require explicit confirmation before all create/update calls and before any status: "publish" action.

Future support for sign-in, teams, richer media, or organizer-specific workflows should be additive:

• Keep setup guidance clear when the MCP connection is missing or unauthenticated.
• Keep the hosted bare MCP URL as the public setup path.
• Add optional arguments or new tools before changing existing tool behavior.
• Read the current project/team state before mutating team-owned projects when the MCP server exposes that data.
• Preserve explicit confirmation before create, update, publish, transfer, invite, or other externally visible actions.