Submit your profile
with your AI agent.

1. Prepare your profile before creating a token

Give your agent the README or website for the projects you want to share. Tell it your preferred name, location, and the tools you actually use. Ask for a specific, factual description of what you build and who it helps.

Copy this prompt into your agent to start:

Help me prepare my profile on Indie Developer (https://www.indiedeveloper.org) using this project’s README and the public links I provide. Draft my bio and project descriptions, suggest accurate tags and tools, and ask me for missing details. Do not invent facts or include private information. Show me the complete draft for review. Do not submit until I explicitly ask you to.

Your bio can be up to 280 characters. Each project needs a name, a description of up to 160 characters, and an HTTPS link. You can include up to 20 projects, eight tags, and eight tools. Your website, social links, avatar, and project images are optional.

2. Connect your agent

Once your draft is ready, sign in with GitHub and expand Submit with an AI agent. Choose Create agent token and copy it immediately; it is only shown once.

In your agent’s MCP settings, add a remote server with these connection details:

Server URL

https://www.indiedeveloper.org/api/mcp/

Transport

Streamable HTTP

Authorization header

Authorization: Bearer YOUR_AGENT_TOKEN

Keep the trailing slash in the URL. Replace the placeholder using your client’s secret or environment-variable settings. Keep the token out of chat prompts, source control, and shared configuration files.

Your client must support Streamable HTTP and a custom Authorization header. Automatic OAuth sign-in is not available for this server. If your client only offers OAuth, use a client with bearer-token support or the website form.

A token lasts 15 minutes and permits one successful write, including an unchanged submission. Create it after drafting. Replacing or revoking it immediately disables the previous token.

3. Review, then submit

After connecting, ask your agent to read your current profile first, reconcile it with your draft, and show you the final content. Keep existing projects and fields you still want. When you are satisfied, tell it to submit.

get_profile

Reads your saved profile, current version, and review status.

submit_profile

Creates or replaces your complete profile. Include all your projects in this one submission.

submit_game

Adds a game to an existing maker profile, or replaces the project with the same exact URL, preserving the rest of your profile.

New profiles go to an administrator for review. A successful submission means your profile was saved, not necessarily published. Return to your submission page to see its status and any reviewer feedback. Edits to an already approved profile publish immediately.

Games submitted through MCP are projects on your maker profile. For a standalone page in the Indie Games showcase, use the game submission form.

4. Keep your listing up to date

When you launch another project or change your bio, create a fresh token and ask your agent to read your profile before editing. For example: “Add this new project to my profile, preserving my existing projects and bio. Show me the change before submitting.”

After a successful write, the token cannot read or edit again. You can still check your saved profile on the website. Use a new token for further agent access.

If something needs fixing

The token expired or has already been used

Create a new token on the submission page and update your client’s secret settings.

Your profile changed since the agent read it

Have the agent read the latest version and reconcile the changes before trying again.

A field fails validation

Correct the reported field and retry. Validation failures do not consume the token.

The response was lost after submitting

Ask the agent to retry the identical operation with the same request ID while the original token is still valid. This retrieves the original receipt without repeating the write.

For agents: every write requires a UUID request_id and the exact version from the latest read. Use null only when creating a new profile. Reuse a request ID only for an identical retry. Leave out github and slug when submitting; your signed-in account determines them.

Need a hand? Contact us, or submit directly through the website.