# Review the focused Workspace connection.

Reviewed: 2026-10-29

Canonical: https://clankercloud.ai/learn/workspace-directory-kits

These directory kits prepare a focused Clanker Cloud Workspace connection and three business role Skills. Use permitted Project sources to prepare saved Markdown and CSV work, record a handoff or save a disabled Agent draft. The files are prepared for review; authenticated client testing, directory submission and publication remain pending.

## What you are working toward

An inspected package, a selected business role and a clear test plan.

## Start with

- A supported assistant client and your chosen Clanker connection

- Permitted Project sources or a deliberately selected fictional packet

- The output, permissions and reviewer for the task

## Choose the connection for the job

The focused connector uses https://workspace.clankercloud.ai/mcp/workspace. It starts with read access; deliberately grant write access when your chosen task needs saved work. Browser authorization belongs to the client’s connection flow. Downloading a kit does not authorize account access or start a task.

This connection provides fixed tools for Project context, UTF-8 files, external-assistant Session records, Planner tasks and disabled Agent drafts. A Session record tracks the assistant’s work; it does not start hosted inference.

| You want to | Focused directory connection |
| --- | --- |
| Use company context | Read permitted Project files and retain source references. |
| Keep the result | Save Markdown or CSV text, verify the returned revision and read the file back. |
| Hand work to an owner | Record the next action and reviewed file paths and revisions in a Planner task. |
| Prepare a reusable specialist | Save an explicitly requested disabled Agent draft with no tools; review it in Workspace. |
| Run Agents or generate Office files | This focused connection does not provide hosted jobs, binary processing, Apps, media, schedules or billing. |

Sources:

- [General assistant connection routes](https://clankercloud.ai/workspace-agents)

- [Workspace capabilities](https://clankercloud.ai/workspace)

## Inspect the package for your client

Version 1.0.0 · reviewed 2026-10-29. Prepared files · client testing and publisher review pending. These are separate directory variants; the existing general-purpose client kits retain their own instructions and capabilities.

The ChatGPT/Codex kit contains a portable manifest, OAuth connection settings and business Skills. The Claude kit contains its native manifest, the same endpoint and the adapted Skills. Both include local workflow instructions, fictional samples and authored review cases. No credentials, live reviewer account or demo recording are bundled.

For Claude publication, the prepared source folder still needs a publisher-approved public repository. This website’s source repository is private. Package preparation is separate from platform review, listing approval and publication.

| Package | Status |
| --- | --- |
| ChatGPT and Codex directory kit | A remote Workspace connector, three business role Skills and authored review cases. Prepared for review; no directory listing or client acceptance is claimed. |
| Claude directory kit | A Claude manifest, the same bounded Workspace connection and business role Skills. Its source folder is staged privately for a future publisher-approved public repository. |

Sources:

- [Download ChatGPT and Codex directory kit](https://clankercloud.ai/downloads/directory-kits/2026-10-29/openai-plugin.zip)

- [Download Claude directory kit](https://clankercloud.ai/downloads/directory-kits/2026-10-29/claude-plugin.zip)

- [Inspect package files, hashes and pending checks](https://clankercloud.ai/downloads/directory-kits/2026-10-29/manifest.json)

- [OpenAI: connect and test a plugin](https://developers.openai.com/plugins/deploy/connect-chatgpt)

- [Claude: structure and testing](https://claude.com/docs/plugins/build)

## Pick a business task with a result you can check

The directory variants use the same fictional source packets as the public role kits, with tasks adapted to this connector’s text-file tools. Start from sources already permitted in the selected Workspace Project, or deliberately choose the included fictional packet.

| Business role | Saved text outputs |
| --- | --- |
| Operations Analyst | capacity-plan.csv and planning-brief.md |
| Client Delivery Assistant | inquiry-tracker.csv and reply-drafts.md |
| Founder’s Research Assistant | research-brief.md |

Sources:

- [Original Operations Analyst role](https://clankercloud.ai/templates/operations-analyst)

- [Original Client Delivery Assistant role](https://clankercloud.ai/templates/client-delivery-assistant)

- [Original Founder’s Research Assistant role](https://clankercloud.ai/templates/founder-research-assistant)

## Review the first task and its saved result

Choose the Project and say which sources the assistant may use. Ask for the required result and name the person who will review it. Setup or permission inspection alone does not create a Project, Session, file or Agent.

When you authorize a saving task, the assistant should use the focused tools and packaged workflow, keep the work in the selected Project and verify the actual saved output. Check the figures, source references and file revision. A proposed reply remains a draft; an Agent draft remains disabled.

Try a correction before using the method with business data. For example, update a fictional service price, then check both the tracker and reply draft. Record what actually happened, including any repair or missing capability. Authored expectations are not a record of a successful client run.

## Keep account access and source material deliberate

Use only sources you are permitted to supply to the selected Workspace Project. The assistant provider’s policies apply independently. ZDR, data residency and encryption are coming soon for Clanker Cloud.

The package does not import Claude memory, chat history, conversation summaries or uploaded client files. Its workflows use selected Workspace Project sources and explicitly requested outputs. Do not grant extra permissions merely to check connection status.

If access is denied, revoked or taken over in Workspace, stop the task and report the state. Do not silently reconnect, switch Projects or retry an uncertain write. Check existing records before repeating an action whose outcome is unclear.

Sources:

- [Current privacy policy](https://clankercloud.ai/privacy)

- [Current service terms](https://clankercloud.ai/terms)

- [Contact support](https://clankercloud.ai/contact)

## What remains before directory publication

Real client acceptance is pending. Reviewers still need a dedicated account with fictional data, recorded tool results, the required positive and negative cases and an accessible walkthrough. Publisher identity, domain verification, current tool and Skill scans and the public Claude source repository also remain to be checked.

The prepared review cases describe expected behavior. They do not establish that ChatGPT, Codex or Claude completed a task, that a platform approved the package or that an assistant recommends Clanker Cloud.

Sources:

- [OpenAI: submission and review requirements](https://developers.openai.com/plugins/deploy/submission)

- [Claude: connector and plugin publication](https://claude.com/docs/directory/publish)

## Common questions

### Are these packages already listed in ChatGPT or Claude?

No. These are prepared directory variants. Directory submission, platform review, publication and authenticated client acceptance remain pending. A download or local package check does not establish a listing.

### Does this replace the existing general-purpose client kits?

No. The existing kits use the broader Clanker connection and retain their own capabilities and testing status. These directory variants use the focused /mcp/workspace endpoint and its fixed Project, text-file, handoff and Agent-draft tools.

### Can this connection generate a spreadsheet workbook or run an Agent?

It can save CSV and Markdown text and a disabled Agent draft. It does not generate XLSX or DOCX files, run hosted jobs or Agents, build Apps, generate media, schedule work or purchase credits. Use Workspace directly for those separate capabilities.

### Does installing the kit create a Workspace Project or grant write access?

No. Client installation, browser authorization and the business task are separate steps. Begin with read access. Deliberately approve the additional write access needed for a task you choose to save.

### Are the planned privacy controls active for this connection?

ZDR, data residency and encryption are coming soon. The assistant provider’s policies and Clanker’s current terms apply independently. Choose material according to the controls available today.

## Sources

- [Workspace support](https://clankercloud.ai/contact)

- [General assistant connections](https://clankercloud.ai/workspace-agents)

- [OpenAI directory requirements](https://developers.openai.com/plugins/deploy/submission)

- [Claude directory requirements](https://claude.com/docs/directory/publish)

## Related

- [Give your next business task a specialist.](https://clankercloud.ai/role-kits)

- [/workspace-agents](https://clankercloud.ai/workspace-agents)

- [Keep the task, progress, and deliverable together in Planner.](https://clankercloud.ai/learn/ai-planner-tasks-and-deliverables)

- [Choose an environment by what the agent must reach.](https://clankercloud.ai/learn/choose-ai-agent-environment)

[Open Workspace](https://workspace.clankercloud.ai)

[Current pricing and usage](https://clankercloud.ai/pricing)