Connect your agent
Codex
First100 lets you run go-to-market from Codex: codex mcp add with the First100 URL, then sign in with codex mcp login or use an API key.
1. What do I need before I start?
Sign in to First100 and choose a plan for the work you want your agent to do. Connect your social accounts before publishing; research does not require a social connection.
Create a key in API key settings and replace f100_your_key in the example. Keep it in your private client configuration.
2. How do I add First100 to Codex?
Two ways. Sign-in (no key): add the server, then run the login command; Codex opens the First100 approval page in your browser and keeps the token refreshed. Or use a key: add the server with the bearer token variable and export FIRST100_API_KEY in the environment that launches Codex. Both commands write ~/.codex/config.toml, which the CLI and the IDE extension share; restart a running Codex afterwards. Check with `codex mcp list`.
codex mcp add first100 --url https://firsthundred.app/api/mcp
codex mcp login first100export FIRST100_API_KEY="f100_your_key"
codex mcp add first100 --url https://firsthundred.app/api/mcp --bearer-token-env-var FIRST100_API_KEY[mcp_servers.first100]
url = "https://firsthundred.app/api/mcp"
# with a key instead of sign-in:
# bearer_token_env_var = "FIRST100_API_KEY"Or skip the file editing: paste this into the agent itself with your key filled in. The agent updates its own configuration, you export the key if it asks, and it reports back once the tools are listed.
Add the First100 MCP server to your own MCP configuration and confirm it works.
Server name: first100
Transport: Streamable HTTP
URL: https://firsthundred.app/api/mcp
Authentication: HTTP header "Authorization: Bearer f100_your_key"
Use whatever config file or command your client uses for remote HTTP MCP servers (for example: Claude Code uses `claude mcp add --transport http`, Codex uses `codex mcp add --url ... --bearer-token-env-var FIRST100_API_KEY` or [mcp_servers.first100] in ~/.codex/config.toml, Cursor uses ~/.cursor/mcp.json). If your client prefers the token in an environment variable, use FIRST100_API_KEY and tell me to export it. Keep any servers already configured.
Then reconnect or reload the MCP servers, list the First100 tools, call get_account_status and list_brands, and show me the result. Do not publish or send anything yet.
Whenever I tell you something shipped or changed in the product, call log_update so the next posts are about it.
From now on: if my account has more than one brand and I have not said which one, ask me before saving, scheduling, publishing or sending anything. Pass the brand name on every First100 call once I have told you, and mention which brand you acted on.For app-specific settings and version differences, see the official setup reference.
3. How do I check the connection?
Use First100 to check my account status and list my connected accounts.The response should show your actual First100 plan and connected platforms. If tools do not appear, enable First100 for the active conversation and reload your client. If access is rejected, reconnect or update your key. See connection help if the issue continues.
4. What should I ask first?
Tell your agent what you built, who it is for, and the outcome you want. Start with research or a draft, then review the next action together.
I’m launching a tool for independent founders. Use First100 to find relevant communities and help me prepare a launch post. Show me the draft before publishing.Explore what your agent can do for more ideas. Agents reading this page can use the agent guide for discovery and working instructions.