almirant init
Configure the Almirant MCP integration for the current repository. This is the all-in-one flow: it includes authentication if needed, account selection, project selection, and configuration generation.
Usage
almirant init [--api-url <url>] [--app-url <url>] [--name <name>]
What it does
- Detects the project type.
- Checks if
.mcp.jsonalready exists and asks whether to continue and merge the Almirant entry. - Lets you select a stored account or add a new one.
- Validates credentials against the server.
- Shows available projects to select or create.
- Generates
.mcp.jsonusingalmirant mcp proxywithout writing tokens. - Copies skills to
.claude/skills/and.agents/skills/.
Generated .mcp.json
{
"mcpServers": {
"almirant": {
"type": "stdio",
"command": "almirant",
"args": ["mcp", "proxy", "--project-id", "<project-id>", "--account", "<account-id>"]
}
}
}
The API key does not appear in the repository. The proxy reads the account from ~/.almirant/config.json and attaches the bearer token in memory only.
When to use init vs link
- Use
initwhen this is your first setup on a machine or you want the CLI to guide you through login. - Use
linkwhen credentials are already stored and you only want to link another repository quickly.