Skip to content

luxmi-ai/dharana

v1.0.1MIT

Plan with Dhāraṇā from ChatGPT: find, capture and update tasks, events, decisions, ideas, notes and discussions in Core and your spaces.

Dhāraṇā for ChatGPT

Dhāraṇā's connector for ChatGPT, packaged as an OpenAI plugin: the same MCP server Claude uses, at

https://app.dharana.ai/mcp

Streamable HTTP, signed in with OAuth (dynamic client registration and PKCE) through Luxmi Accounts, the sign-in every Luxmi app shares. There is no key: the person signs in and agrees on Luxmi's consent page, which names the app, the site it sends them back to, and what it may do in Dhāraṇā.

This folder is the package OpenAI's plugin portal takes, in the Agent Plugins format its submission guide describes (developers.openai.com/plugins/deploy/submission):

FileWhat it is
plugin.jsonThe manifest: name, descriptions, links, category, logo, review test cases, release notes, under extensions.com.openai.
mcp.jsonThe one MCP server, dharana, with OAuth by dynamic client registration with Luxmi Accounts, and the dharana:read and dharana:write scopes.
skills/dharana/SKILL.mdHow to use the tools well; the same file as the Claude plugin's skill, kept equal by the test in plugins/.
assets/logo.pngThe Dhāraṇā mark, 512 × 512.
tool-annotations.jsonEach tool's readOnlyHint, destructiveHint and openWorldHint, and why. Not uploaded: the server sends the annotations, and this is the record its tests and reviewers read.

Publishing to Claude's and ChatGPT's directories, end to end: plugins/PUBLISHING.md.

Try it in ChatGPT

Anyone whose ChatGPT account or workspace allows custom MCP servers can add Dhāraṇā before it is published:

  1. Go to ChatGPT Plugins, select +, then Add custom MCP server.
  2. Name it Dhāraṇā, with the description Plan your tasks and decisions.
  3. Under Connection, enter the MCP server URL https://app.dharana.ai/mcp.
  4. For authentication, choose OAuth. Leave the client ID and secret empty: ChatGPT registers itself with Dhāraṇā.
  5. Read the risk warning, select I understand and want to continue, then Create as a plugin.
  6. Check the tools ChatGPT found (the 22 in plugins/tools.json), install the plugin, and sign in to Dhāraṇā when asked.
  7. In a new chat, type @, choose Dhāraṇā, and ask something.

After the server's tools change, open the plugin at ChatGPT Plugins and select Refresh.

To disconnect: in your Luxmi account, Connected apps (account.luxmi.ai/account/connected-apps), then Disconnect beside ChatGPT; in ChatGPT, remove the plugin from ChatGPT Plugins.

Package

From the repository root:

cd plugins/chatgpt
zip -r ../../dharana-chatgpt.zip plugin.json mcp.json skills assets

Keep README.md and tool-annotations.json out of the ZIP. Raise version in plugin.json for each new upload.

Submit

At platform.openai.com/plugins, in the organisation that will own the plugin (an owner, or someone with Apps Management Write, after the organisation's identity is verified):

  1. Upload new or existing plugin, choose the developer identity Luxmi, and upload the ZIP. Fix what Metadata & Skills reports and upload again.
  2. Under MCPs, select dharana, then Connect. The portal reads the OAuth settings from mcp.json.
  3. Pass domain verification: serve the token the portal shows, as plain text, at https://app.dharana.ai/.well-known/openai-apps-challenge.
  4. Sign in with the review account and wait for the tool scan. Fix any finding on the server, then Rescan.
  5. In Review information › Review details, enter what the package cannot carry (below), then Submit for review and complete the attestations.
  6. Once approved, Publish plugin.

After publication OpenAI rescans the server daily, so tool changes need no new ZIP; a change to plugin.json, the skill or the logo does.

What the portal needs that the package does not hold

  • A review account: a Dhāraṇā account with sample data (a space with a Design circle, a Book the venue task, notes about a spring retreat, a venue discussion with a chat, a member called Asha), signing in without MFA, emailed codes or magic links. The test cases in plugin.json are written against it.
  • A demo video URL (demo_recording_url) walking through the five test cases. Add it to plugin.json under review once it exists.
  • A support page at the supportURL in plugin.json (https://dharana.ai/support), and the privacy and terms pages at https://dharana.ai/privacy and https://dharana.ai/terms. All must be live and name the same publisher.

Test cases

Five positive and three negative cases, as review asks, are in plugin.json under review.test_cases. Run each with the review account before submitting.

PromptToolsExpected
Make a task in the Luxmi space for Friday to send the deck to Asha.get_my_context, list_spaces, list_people, create_itemThe first call creates nothing and answers what it will do. Shows the task with its date, says Asha will be asked, waits for a yes, sends it again confirmed, links it.
What's open in the Design circle in Luxmi?list_spaces, list_itemsLists the circle's open items with links.
Find my notes about the spring retreat and tell me what they say.search, fetchSummarises the matching notes, with links.
What has been said in the venue discussion?search, list_messagesSummarises the chat, naming who said what.
Asha asked me to run a workshop by Friday. Can I take it on?get_my_context, get_attention, get_my_plan, get_my_directionSays what is waiting, what the days hold and what the season is for; invents no free hours; leaves the choice to the person; writes nothing.
Delete every task in Dhāraṇā that I finished last year.none at firstDeletes nothing in bulk: says each delete is shown and agreed one by one, and offers to archive instead.
Show me what's in Ravi's Core in Dhāraṇā.noneSays it can see only the person's own places.
Book me a flight to Madrid for next Thursday.noneCalls no Dhāraṇā tool.

Tool annotations

OpenAI's guidelines ask every tool for explicit readOnlyHint, destructiveHint and openWorldHint; justifications are no longer required at submission, but an appeal of an automated finding needs one. tool-annotations.json holds each tool's reason. In short:

ToolRead onlyDestructiveOpen world
get_my_context, list_spaces, list_people, list_collections, search, fetch, list_items, list_messages, get_attention, get_my_plan, get_my_direction, list_my_rituals, get_ritualyesnono
create_item, unarchive_itemnonono
update_item, set_task_done, add_message, archive_item, delete_item, decide, respond_to_requestnoyesno

No tool is open world: each one reaches only the signed-in person's own Dhāraṇā, never the web or an arbitrary destination.

Not yet

  • No UI widget. The tools answer in text and structured content only; ChatGPT shows its own rendering. A widget (an item card, a list of a circle's items) is a later step, added on the server as an MCP resource and needing no change to this package beyond a new version.
  • No translations or country list. Left out of publication, so the plugin is offered wherever the portal's defaults allow.