SparkGlim integrations
SparkGlim for Codex
Understand the separate Codex client-compatibility and availability requirements before attempting an organizer account connection.
Availability is controlled separately
Codex has its own integration record. If it is disabled or under maintenance, this page provides documentation rather than an installation or connection action.
MCP support is not compatibility approval
A client must meet SparkGlim’s approved OAuth, signing and configured transport requirements. A generic MCP connection or shared server URL does not prove it can complete that flow.
Keep the organizer contract intact
When a client is approved and enabled, access still follows consent, account permissions and assigned campaigns. The integration does not become an unrestricted developer or database tool.
Use public developer guidance meanwhile
The Developer AI hub can prepare a public coding brief for Codex without connecting an organizer account. That is a separate resource, not a workaround for a disabled plugin.
An AI prompt is a different tool.
The Developer AI hub prepares public integration instructions for several assistants. It does not install a SparkGlim app, connect an account or make an unapproved client compatible.
Questions before setup
Can I connect while Codex is disabled?
No. The registry must enable the integration and the client must support SparkGlim’s approved authentication. A public product page does not grant access.
Does a coding prompt connect my creator account?
No. Developer prompts contain public implementation guidance. They do not perform OAuth, grant scopes or read private campaigns.
Who controls campaign and payment access?
SparkGlim Server applies consent, role and campaign permissions. Connected organizer tools do not process payments, withdraw funds or check attendees in.