> For the complete documentation index, see [llms.txt](https://docs.cheqd.io/product/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cheqd.io/product/getting-started/ai-agents/trust-registry/setup-mcp/import-credential.md).

# Import Credential to AI Agent

Accept a JWT Credential into the AI Agent's wallet.

As per [our instructions](/product/getting-started/ai-agents/trust-registry/setup/issue-credential.md) on issuing a verifiable credential to your AI Agent, you can now use the Agent's DID as the `subjectDID` to create an accreditation for the agent using Cheqd Studio. The response from [Step 4](/product/getting-started/ai-agents/trust-registry/setup/issue-credential.md#step-4-issue-verifiable-credential-to-ai-agent) will include a JWT token in the `proof` section.

Copy the JWT token and ask Claude Desktop (or any your choice of MCP Client) to accept the credential as follows:

> Can you accept the credential from this JWT token "eyJhbGciOiJFZ....."

Claude/Client should use the `import-credential` tool to add this credential to it's wallet as shown below:

<figure><img src="https://3569764573-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPVAMvpKH7PYzvXA6u6Cn%2Fuploads%2FcESZpAP4TQMv5Hr30x3W%2FScreenshot%202025-05-01%20at%2016.39.07.png?alt=media&amp;token=85f69f7c-800c-4994-b502-068897a795ab" alt=""><figcaption></figcaption></figure>

## What is happening under the hood?

In the background, Claude is communicating with our MCP Server which relays a request to one of our SDKs, [Credo](/product/sdk/credo.md). Using Credo, the AI Agent imports a Credential into the identity wallet associated with itself.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cheqd.io/product/getting-started/ai-agents/trust-registry/setup-mcp/import-credential.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.