Create a Custom Project with MCP

BLSFlow MCP lets Codex and other MCP clients create a private custom project, its pools, parameter definitions, and runtime scripts after you authorize access in the browser.

For manual script changes, see Create a Custom Project.

Before you start

Prepare the official project website or repository, a trusted Linux miner download, the pool connection format, and the required wallet, worker, and password parameters.

Sensitive values

Never ask AI to guess a wallet, password, private key, or token. User-specific values must remain runtime parameters and must not be hard-coded in a project script.

Configure BLSFlow MCP

Add the following server to ~/.codex/config.toml:

[mcp_servers.blsflow]
url = "https://mcp.blsflow.com/mcp"
auth = "oauth"
default_tools_approval_mode = "writes"

Check the configuration and sign in:

codex mcp list
codex mcp login blsflow

The browser authorization page asks for permission to create custom projects, pools, and private runtime scripts. OAuth does not require you to paste a console token into Codex or a chat.

Ask Codex to create the project

Provide confirmed source information and ask Codex to show missing information before writing anything:

Create a custom project through BLSFlow MCP.

- Project: Example Coin
- Symbol: example
- Algorithm: randomx
- Website: https://example.org
- Repository: https://github.com/example/example
- Systems: Ubuntu 22.04+ and Ubuntu 24.04+
- Pool: stratum+tcp://pool.example.org:3333
- Linux miner: https://example.org/releases/miner-linux.tar.gz
- Executable: example-miner
- Arguments: -o pool, -u wallet.worker, -p x

Keep the wallet as a required runtime parameter. Ask me to confirm any
missing information before creating the project.

Codex normally uses create_custom_project. For an existing project that needs another pool, it uses add_project_pool. Prefer structured managed_miner input; provide a full script_content only when installation, configuration generation, dependencies, or hashrate parsing require custom logic.

Verify the result

In the console, confirm the project metadata, pool protocol and address, runtime parameters, private script ownership, trusted download URL, and executable name.

Then switch only one test device and inspect it:

systemctl status blsflow-miner-example.service --no-pager
journalctl -u blsflow-miner-example.service -n 100 --no-pager
bash /opt/blsflow/run/example/hashrate.sh

Confirm that the miner connects with the intended wallet and worker and that hashrate.sh prints a numeric kH/s value before deploying to more devices or enabling scheduling.

Troubleshooting

• No authorization support detected: verify the MCP OAuth metadata endpoints under https://mcp.blsflow.com/.well-known/ and make sure the reverse proxy forwards /.well-known/* and /oauth/*.
• login_required: sign in to the BLSFlow console again and retry authorization.
• BLSFlow tools are missing: run codex mcp list, confirm the server is enabled, and restart the Codex client.
• The miner does not start: check the download URL, archive layout, executable name, and launch arguments. Use the manual guide for custom installation or log parsing.