lookahead-mcp
Connect Claude Desktop, or another MCP-compatible AI assistant, to your wardrobe in The Lookahead. Once connected, you can ask your assistant about your wardrobe and your week's outfits, or ask it to plan your week.
Connecting an AI assistant is part of The Lookahead Pro.
What your assistant can see and do
- See your wardrobe list (category, main colour, brand), this week's plan, and a summary of what your wardrobe covers.
- Do one thing: ask for a new weekly plan. That counts against your normal plan allowance, just like planning in the app.
- Never see your photos, your name, email, location or payment details, or anyone else's information. It can't change your wardrobe or settings.
You can disconnect at any time in the app. The full details are in section 7.5 of our privacy policy.
Set it up (Claude Desktop)
-
Install uv, a small tool that runs Python programs for you. On a Mac, open Terminal and run:
curl -LsSf https://astral.sh/uv/install.sh | sh
On Windows, see uv's install page.
-
Add The Lookahead to Claude Desktop. In Claude Desktop, open Settings → Developer → Edit Config and add this to the file:
{ "mcpServers": { "lookahead": { "command": "uvx", "args": ["lookahead-mcp"] } } }
If the file already has an
mcpServerssection, add just the"lookahead"entry inside it. Save, then quit and reopen Claude Desktop. -
Connect your account. Ask Claude something like "What's in my Lookahead wardrobe?" Claude will show you a code such as
ABCD-2345. -
Approve it in the app. Open The Lookahead, go to Settings → Connect an AI agent, and enter the code. It's valid for 10 minutes.
-
Ask again. Tell Claude you've entered the code, and ask your question again. You're connected, and you won't need to do this again unless you disconnect.
If uvx isn't found after installing uv, use its full path in the config
instead (run which uvx in Terminal to find it).
Disconnecting
In The Lookahead, go to Settings → Connect an AI agent → Disconnect.
Access stops immediately. To remove the connector too, delete the
"lookahead" entry from Claude Desktop's config and delete the
~/.lookahead-mcp folder.
Tools
get-wardrobe— your active wardrobe.get-current-plan— this week's outfit plan.get-coverage— what your wardrobe covers (tops or dresses, bottoms, shoes, outer layers).generate-plan— make a new weekly plan.
Development
uv sync --group dev
uv run pytest
LOOKAHEAD_MCP_BASE_URL points it at a non-production backend, and
LOOKAHEAD_MCP_CONFIG_DIR changes where the credential file is stored.
Release files for lookahead-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| lookahead_mcp-0.1.0.tar.gz | 75.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| lookahead_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 85.0 kB
Release files / lookahead_mcp-0.1.0.tar.gz
| Download URL | lookahead_mcp-0.1.0.tar.gz |
|---|---|
| Size | 75.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ca2433a3a540dc946c8197bb48b13fbf3aa7ca3a7fa436b975fad3f3a5254195
|
|
BLAKE2b-256 checksum How to use checksums |
198a6c749f3d10c12cb5d92ae1cfe27a0be8b0873cb8f88068d818406c487ba2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 26, 2026.
Transparency logRelease files / lookahead_mcp-0.1.0-py3-none-any.whl
| Download URL | lookahead_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 9.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8d630290dc70928d0655f357087acfdccbb8f34ca6ab8002a786521cfa113327
|
|
BLAKE2b-256 checksum How to use checksums |
4f8f3af3e39f1bdf936d48fc378ba470ff9fef9c7621978c9380df16a931efd4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 26, 2026.
Transparency log