MYASP.NET MCP · BETA
BetaConnect OpenAI Codex
Codex can discover and call the myASP.NET Beta tools directly from your development workflow. The API key stays in an environment variable; it is not written into config.toml.
1. Set the environment variable
macOS / Linux
export MYASP_API_KEY="paste-your-key-here"PowerShell
$env:MYASP_API_KEY = "paste-your-key-here"2. Configure the remote MCP server
~/.codex/config.toml
[mcp_servers.myasp]
url = "https://mcp.site4now.net/mcp"
bearer_token_env_var = "MYASP_API_KEY"3. Start with read-only discovery
Prompt
Use the myASP.NET MCP. List my accounts, existing hosting plans, websites, databases, and email domains. Do not change anything.4. Ask for an explicit plan before writes
For changes, tell Codex which resource to use and ask it to show the intended operations first. Destructive tools require exact identifiers and explicit acknowledgements, but reviewing the plan remains a good practice.
Prompt
On my existing Linux plan, create a website named inventoryapi. Before making changes, show me the selected plan ID, expected result, and follow-up deployment steps.No Codex OAuth login
The Beta connection uses the API key configured above. You do not need to run an MCP OAuth login command.