[Integrations](https://spiral.ai/integrations) › [Grok](https://spiral.ai/integrations/grok) › [Claude Code configuration reference](https://spiral.ai/integrations/grok/claude-code-configuration-reference)

# How to Use Claude Code configuration reference in Grok

Returns reference tables for Claude Code settings, hook events, environment variables, and skill and subagent frontmatter. Use it to find documented configuration names before reading their behavior in full.

|  |  |
| --- | --- |
| Model | Claude Code configuration reference |
| Available through | Alexandria |
| Category | Developer |
| Price | $0.00873 per call. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, no API key |

## Prompts to try with Claude Code configuration reference in Grok

- Use Claude Code configuration reference to find entries about permissions and explain what each documented name refers to.
- Use Claude Code configuration reference to look this up and give me the result as a table.
- Pull the latest numbers from Claude Code configuration reference and tell me what changed since last week.
- Check Claude Code configuration reference and summarize what you find in three bullet points.
- Pull the newest data from Claude Code configuration reference and give me the result as a table.

## How to set up Claude Code configuration reference in Grok

Pick the way that suits you. Each takes about two minutes.

### Use the Grok connector

1. **Add a custom connector**: In Grok open Settings › Connect Apps, then Add a custom connector. Name it Spiral, paste this URL, leave Headers empty and click Add MCP.

```text
https://api.spiral.ai/mcp
```

2. **Sign in to Spiral and approve**: Grok opens Spiral: sign in, pick the organization and click Authorize. Spiral gives the connection its own API key; Grok never sees it, and you can remove the connection under Settings › Connected apps.

3. **Check that it is connected**: Connect Apps › Custom shows Spiral as Connected. It works in every Grok chat and Grok bot.

### Use the Spiral skill

1. **Send Grok this message**: Your agent reads Spiral's skill and sets itself up.

```
set up https://spiral.ai/SKILL.md
```

2. **Sign in or paste a key**: Approve Spiral in the browser, or give the agent a key from the console.

### Use the Spiral CLI

1. **Install and sign in**: Installs the Spiral CLI, signs you in and adds its skill to your coding agents.

```bash
npx -y spiral-cli@latest init
```

### Call the Spiral API

1. **Create an API key**: In the console, under API keys.

2. **Run Claude Code configuration reference**: One request; the result comes back by polling or a webhook.

```bash
curl https://api.spiral.ai/v1/runs \
  -H "Authorization: Bearer $SPIRAL_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "provider": "alexandria",
    "model": "code-claude-com/developer-documentation/config_reference",
    "input": {
      "kind": "settings"
    }
  }'
```

Then paste one of the prompts above: Grok finds Claude Code configuration reference on Spiral, shows the price and runs it.

Setup guide in the docs: https://spiral.ai/docs/quickstarts/grok

## Claude Code configuration reference tools and prices

- [Claude Code Docs · Config reference](https://spiral.ai/tools/alexandria/code-claude-com/developer-documentation/config_reference) (Alexandria): $0.00873 per call.

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| q |  | — | Case-insensitive substring matched against name and description. |
| limit | 1 to 1000 | — | Defaults to 500. |
| offset | 0 to 100000 | — | Defaults to 0. |

## What can you do with Claude Code configuration reference in Grok?

Get a reference-backed explanation of a Claude Code problem, such as conflicting settings or a hook failure. A chat app can turn published documentation and release history into a focused answer with links to the relevant material.

### Review a Claude Code upgrade

Find release changes affecting hooks and settings, locate the relevant documentation, check configuration names, and read the explanations needed for an upgrade checklist.

### Write a hook troubleshooting guide

Map the hook documentation, find event references and relevant sections, and check release notes for changes that could explain a reported failure.

### Review team configuration guidance

Collect the settings and precedence pages, look up documented keys, and review release changes before revising a team's Claude Code policy guide.

### Maintain a skill authoring handbook

Find the skill documentation and frontmatter reference, read the relevant sections, and review release notes before updating authoring examples.

### Prepare a support investigation

Search a reported Claude Code issue, retrieve the supporting documentation, check configuration terminology, and inspect release notes for a related fix.

## Overview

- [Alexandria](https://spiral.ai/providers/alexandria)
- [All Grok guides](https://spiral.ai/integrations/grok)

## Claude Code configuration reference in other agents

- [Amp](https://spiral.ai/integrations/amp/claude-code-configuration-reference)
- [ChatGPT](https://spiral.ai/integrations/chatgpt/claude-code-configuration-reference)
- [Claude](https://spiral.ai/integrations/claude-desktop/claude-code-configuration-reference)
- [Claude Code](https://spiral.ai/integrations/claude-code/claude-code-configuration-reference)
- [Cline](https://spiral.ai/integrations/cline/claude-code-configuration-reference)
- [Codex](https://spiral.ai/integrations/codex/claude-code-configuration-reference)
- [Cursor](https://spiral.ai/integrations/cursor/claude-code-configuration-reference)
- [Devin](https://spiral.ai/integrations/devin/claude-code-configuration-reference)
- [dots](https://spiral.ai/integrations/dots/claude-code-configuration-reference)
- [Factory Droid](https://spiral.ai/integrations/factory-droid/claude-code-configuration-reference)
- [Gemini](https://spiral.ai/integrations/gemini/claude-code-configuration-reference)
- [Gemini CLI](https://spiral.ai/integrations/gemini-cli/claude-code-configuration-reference)
- [Google Antigravity](https://spiral.ai/integrations/antigravity/claude-code-configuration-reference)
- [goose](https://spiral.ai/integrations/goose/claude-code-configuration-reference)
- [Grok Build](https://spiral.ai/integrations/grok-build/claude-code-configuration-reference)
- [Hermes](https://spiral.ai/integrations/hermes/claude-code-configuration-reference)
- [Instinct](https://spiral.ai/integrations/instinct/claude-code-configuration-reference)
- [Manus](https://spiral.ai/integrations/manus/claude-code-configuration-reference)
- [Muse](https://spiral.ai/integrations/muse/claude-code-configuration-reference)
- [Muse Code](https://spiral.ai/integrations/muse-code/claude-code-configuration-reference)
- [n8n](https://spiral.ai/integrations/n8n/claude-code-configuration-reference)
- [Notion](https://spiral.ai/integrations/notion/claude-code-configuration-reference)
- [OpenClaw](https://spiral.ai/integrations/openclaw/claude-code-configuration-reference)
- [opencode](https://spiral.ai/integrations/opencode/claude-code-configuration-reference)
- [Perplexity](https://spiral.ai/integrations/perplexity/claude-code-configuration-reference)
- [Raycast](https://spiral.ai/integrations/raycast/claude-code-configuration-reference)
- [VS Code](https://spiral.ai/integrations/vscode/claude-code-configuration-reference)
- [Windsurf](https://spiral.ai/integrations/windsurf/claude-code-configuration-reference)
- [Zapier](https://spiral.ai/integrations/zapier/claude-code-configuration-reference)

## More Grok guides

- [Claude API release notes](https://spiral.ai/integrations/grok/claude-api-release-notes)
- [Claude Code documentation index](https://spiral.ai/integrations/grok/claude-code-documentation-index)
- [Claude API endpoint reference](https://spiral.ai/integrations/grok/claude-api-endpoint-reference)
- [Claude Code documentation page](https://spiral.ai/integrations/grok/claude-code-documentation-page)
- [Claude (claude.com) Search docs](https://spiral.ai/integrations/grok/claude-claude-com-search-docs)
- [Claude Code documentation search](https://spiral.ai/integrations/grok/claude-code-documentation-search)

## Questions about Claude Code configuration reference in Grok

**Can Grok use Claude Code configuration reference?**

Yes. Add Spiral to Grok as an MCP server, and Grok can find and run Claude Code configuration reference like any built-in tool.

**How much does Claude Code configuration reference cost in Grok?**

$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Grok plan is separate.

**Do I need an Alexandria account to use Claude Code configuration reference in Grok?**

No. Spiral runs Claude Code configuration reference on its own Alexandria account. You sign in to Spiral once and never paste a key.

**How long does it take to set up Claude Code configuration reference in Grok?**

About two minutes: add a custom connector, then sign in to Spiral and approve, then check that it is connected.

**Does Grok wait while Claude Code configuration reference runs?**

Claude Code configuration reference runs in the background. Grok starts the run, checks on it and gives you the json when it's ready.

**What does the Claude Code documentation cover?**

The official index covers configuration, skills, subagents, hooks, MCP, and the Agent SDK. This is the Claude Code documentation corpus.

**Does this data show my organization's actual configuration?**

The source is published documentation at code.claude.com. Its configuration references describe documented settings and behavior; they do not inspect your organization's installation.

**Does documentation search cover the whole web?**

Anthropic describes its documentation MCP server as providing full-text search over Claude Code docs. Its search coverage is the documentation corpus.

**How recent is the published release information?**

When checked on November 20, 2026, the official changelog included version 2.1.329 dated November 19, 2026. That establishes the recency of the published release history at that check.

**How far back does the release history go?**

The published changelog reaches back at least to version 0.2.21, dated April 2, 2025. This is release history, rather than an archive of every earlier documentation revision.

