How project teams use the OpenNomos MCP to view, review, and manage growth opportunities programmatically.

Manage Opportunities via MCP

Project teams can use the OpenNomos MCP to view and manage opportunities programmatically — through an agent, a script, or direct HTTP calls.

This page covers the project-side endpoints: viewing opportunities, updating reviews, and checking daily operational metrics.

Prerequisites

First, download the reusable OpenNomos MCP skill so your agent knows how to call the endpoints below:

https://github.com/NomosGrowth/opennomos-mcp-skills

git clone https://github.com/NomosGrowth/opennomos-mcp-skills.git
mkdir -p "$CODEX_HOME/skills"
cp -R opennomos-mcp-skills/skills/* "$CODEX_HOME/skills/"

The included skill opennomos-agent-mcp teaches agents how to call the MCP endpoints in this guide. To update the skill later, run git pull in the cloned directory and copy the files again.

You also need an MCP API Key (starting with nk_).

Create it from:

OpenNomos website -> Profile -> MCP Access -> Create key

Or open it directly after logging in:

https://www.opennomos.com/en/me/mcp-access

Copy the key immediately after creating it — it is shown only once. Store it in your agent configuration or environment, and do not post it in public pages, chats, or repositories.

All requests use the base URL https://api.opennomos.com and authenticate with:

Authorization: Bearer <your_nk_key>

Viewing Opportunities

Use this endpoint to see the growth opportunities submitted for your project:

GET /api/v1/mcp/projects/:project_id/opportunities

curl -sS \
  -H "Authorization: Bearer $TOKEN" \
  "$BASE_URL/api/v1/mcp/projects/<project_id>/opportunities?date=all&page=1&page_size=20"

Common filters:

Filter	Values
`type`	`all`, or a specific opportunity type such as `potential_user_opportunity`
`date`	`all` or `today`
`evaluation`	`all`, `useful`, or `not_useful`
`status`	`all`, `pending`, `reviewing`, `contacted`, `adopted`, `ignored`, or `done`
`page`, `page_size`	Pagination controls

Each opportunity includes its event_id, contribution_type, key_information, reason, suggested_action, received_at, plus the current review state (evaluation, status, review_note).

This endpoint requires project review access. If it returns 403, your key is valid but does not have review access for this project.

Updating a Review

To mark an opportunity as useful, change its status, or add a note, update its review:

PATCH /api/v1/mcp/projects/:project_id/opportunities/:event_id/review

curl -sS -X PATCH \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "evaluation": "useful",
    "status": "adopted",
    "note": "Useful lead. Contacted and moved into follow-up."
  }' \
  "$BASE_URL/api/v1/mcp/projects/<project_id>/opportunities/<event_id>/review"

You only need to send the fields you want to change. Omitted fields are preserved.

Field	Values	Notes
`evaluation`	`useful`, `not_useful`, or empty string	Empty string clears the evaluation
`status`	`pending`, `reviewing`, `contacted`, `adopted`, `ignored`, `done`	Track progress through your pipeline
`note`	Free-form text	Reviewer-facing reason or next-step note, max 2000 characters

After the update, the response returns the updated evaluation, status, review_note, and review_updated_at.

Only update reviews when you actually want to change project-side state — this is a write action.

Daily Operational Metrics

You can also inspect how your project is performing day by day.

Project overview

GET /api/v1/mcp/projects/:project_id/overview

KPI and overview data for the project.

Daily ops

GET /api/v1/mcp/projects/:project_id/daily-ops

curl -sS \
  -H "Authorization: Bearer $TOKEN" \
  "$BASE_URL/api/v1/mcp/projects/<project_id>/daily-ops?window=7d"

Returns daily registration and usage metrics:

registered_users — unique users who signed up that day
daily_use_users — unique users active that day
active_users — currently the same as daily_use_users
signup_events / daily_use_events — raw event counts

Use window=7d for a recent trend, or window=30d for a monthly view.

Daily event summary

GET /api/v1/mcp/projects/:project_id/daily-event-summary

Per-day event counts and unique-user counts, grouped by event name. Useful for seeing which actions drive volume.

Event stream

GET /api/v1/mcp/projects/:project_id/event-stream

Returns the current authenticated user's recent raw events for this project. Use this to check whether a specific event was recorded.

Common Agent Prompts

If you use an agent (such as Claude Code or Codex) with the OpenNomos MCP, you can send prompts like:

Show me today's opportunities for this project.
List opportunities that are still pending.
Mark this opportunity as useful and set status to contacted.
Show the daily ops for the last 7 days.

Connect Claude or Codex — run the same inbox from an agent.
Opportunity inbox — review and update opportunities in Studio.

Manage Opportunities via MCP

On this page