Set up Amazon Bedrock AgentCore
Add Charming as an external MCP server target in an AgentCore Gateway.
You need an AgentCore Gateway and permission to manage targets and credentials.
Get a Charming token
Start a device pairing from a terminal:
curl -sS -X POST https://charm.ing/api/pair/start \
-H 'Content-Type: application/json' \
-d '{"label":"Amazon Bedrock AgentCore"}'
Open charm.ing/pair, enter the user_code from the response, and approve access. Then poll with the device_code:
curl -sS -X POST https://charm.ing/api/pair/poll \
-H 'Content-Type: application/json' \
-d '{"device_code":"PASTE_DEVICE_CODE"}'
Copy the chrm_user_* token from the first approved response. Charming returns it once.
Add Charming as a target
-
Open your AgentCore Gateway.
-
Add an MCP server target.
-
Set the server URL to:
https://charm.ing/mcp -
Choose API key authorization and create an AgentCore API key credential provider with the
chrm_user_*token. -
Set the credential location to the
Authorizationheader and the credential prefix toBearer. -
Grant the gateway role access to the credential provider.
-
Synchronize the target and wait for its status to become ready.
-
Add the gateway to your AgentCore agent and test
list_apps.
AgentCore calls Charming’s tools. Finished apps open at their Charming URL.
See AWS’s guides for external MCP server targets and target authorization.
Paired tokens expire after 30 days. Pair again to replace one, then revoke the old token on your Connections settings.
Build without an MCP target
The chrm_user_* token above is not limited to MCP. An AgentCore agent that makes its own outbound HTTP requests can call Charming’s HTTP API with the same Authorization: Bearer header and skip the gateway target. The routes are in Build over the HTTP API.
Give the agent this instruction:
Use Charming's HTTP API with the chrm_user_* token I gave you. Read
https://charm.ing/docs/build-http.md, then ask me what I want to build.
Both paths build the same apps in the same account.