# Chroma - vector server - Credential setup | Docs - nodulz

Source: https://nodulz.com/docs/credentials/chroma

Language: en

Credential type in nodulz : `vector:chroma`.

## Create access

Ask the administrator for a compatible Chroma server and a collection reachable from the backend. Set its URL and collection identifier in nodulz.

## Configure in nodulz

In your instance, open Credentials, select the type above, name the credential and complete these fields:

```text
apiKey, host, indexName
```

Save the credential, then select it on relevant nodes. URLs or parameters marked as node settings belong directly on that node.

## Things to check

The code targets /api/v1/collections/{collection} and does not send the stored API key for these calls. The form still requires a key. Cloud or API v2 deployments may need an adapter; do not assume compatibility.

Verify an operation with expected permissions and data before publishing. Keep secrets out of logs and revoke them with the provider when no longer needed.

## Official references

- [Provider documentation](https://docs.trychroma.com/)

See also : [Credentials and rotation](/docs/credentials), [Node catalog](/docs/nodes).

## Explore further

- [Features - nodulz](https://nodulz.com/product/overview)
- [Node catalog - nodulz](https://nodulz.com/product/catalog)
- [MCP server - nodulz](https://nodulz.com/product/mcp)
- [Pricing - nodulz](https://nodulz.com/pricing)
- [Use cases and workflow automation - nodulz](https://nodulz.com/use-cases)
- [Choose what your workflows can do. - nodulz](https://nodulz.com/compare)
- [Documentation - nodulz](https://nodulz.com/docs)