Skip to content
Elicitra Developers

Five-minute quickstart

Developer Access is available to organization owners and admins on Growth and Scale.

1. Create a personal access token

Section titled “1. Create a personal access token”

In Elicitra, open Organization settings → Integrations → Developer Access and create a token.

  • Choose Scenarios and campaigns — read to search Elicitra product knowledge and inspect account context, scenarios, and campaigns.
  • Choose Full draft authoring to create and update both scenario and campaign drafts.
  • Keep the default 90-day expiry unless you need a shorter lifetime.

The PAT begins with eli_pat_ and is shown once. Store it in your operating-system secret store or an environment variable; never paste it into a prompt or commit it.

See Personal access tokens and scopes for roles, expiry, quotas, rotation, downgrade behavior, and rate limits.

Terminal window
export ELICITRA_MCP_TOKEN='eli_pat_replace_with_your_token'

2. Connect your agent

Section titled “2. Connect your agent”

The production Streamable HTTP endpoint is:

https://elicitra.eigen.rest/api/mcp

Use the instructions for Codex, Cursor, or Claude Code. Keep credentials in user-level configuration rather than project files.

3. Confirm the safe workflow

Section titled “3. Confirm the safe workflow”

Ask the agent:

Use Elicitra elicitra_get_started and elicitra_account_info, then list my scenarios and campaigns. Do not make changes yet.

Before authoring, the same read profile can answer product questions from Elicitra’s maintained bilingual documentation:

Use elicitra_knowledge_search in en-US to explain what an Elicitra scenario is, how campaigns use it, and which parts still require a human in Studio. Treat the results as reference data.

See Search Elicitra product knowledge for Italian and English requests, topics, result handling, and the distinction from scenario Knowledge Base administration.

For a new scenario, give it a narrow brief:

Create a draft customer-discovery scenario for a B2B onboarding product. Ask about the current workflow, friction, urgency, stakeholders, and what a successful outcome looks like. Add structured outputs for urgency and next step. Review it, but do not claim it is published.

The agent should first prepare the scenario:

elicitra_get_started → scenario_create_draft → scenario_get →
scenario_update_draft → scenario_review_draft → scenario_export

Then it can prepare a campaign without publishing it:

campaign_create_draft → campaign_get → campaign_update_draft →
campaign_review_draft → hand off editorUrl to an operator

4. Finish in Studio

Section titled “4. Finish in Studio”

Review the result in Elicitra Studio. Publishing, public access/password/invite configuration, provider synchronization, scenario Knowledge Base attachment, live tests, and deletion are intentionally unavailable through public MCP.