Repository clone/fetch/write needs, branch scope, token or key ownership, webhooks, and revocation. Verify each provider and auth method.
INTEGRATION GUIDE · VERIFIED 2026-08-05
Integrations are permissions and data routes, not just logos.
MonkeyCode workflows require repository access, model access, development infrastructure, and supporting network services. Public materials do not establish a complete provider-by-provider compatibility matrix, so this page separates documented categories from items that must be verified.
DIRECT ANSWERModel management and repository-connected development are part of the documented platform model.
The current public README names GLM, Kimi, MiniMax, Qwen, and DeepSeek model families. Exact Git providers, authentication methods, model versions, endpoints, regions, quotas, and support status must be confirmed in the current release and documentation.
Connection inventory
Four boundaries to document.
For each connection record the owner, credential, permission, endpoint, data sent, retention, failure behavior, and revocation procedure.
Exact model ID, provider or private endpoint, credential, context sent, retention terms, quota, fallback, and cost.
Console and environment hosts, DNS, TLS, storage, image/package access, previews, logging, and backups.
GitHub Issues and Discord are support/community channels, not runtime product integrations.
Verification matrix
Do not convert an architecture need into a compatibility claim.
Only mark an integration supported after testing the exact release and authentication path.
| Claim | Status on this page | How to verify |
|---|---|---|
| Model families named in public README | Documented | Check current README and installation configuration |
| Repository access is required for repository work | Workflow requirement | Test least-privilege read/write behavior |
| Specific Git provider support | Not claimed | Find current official provider documentation and run a test |
| Specific webhook/OAuth/SSH behavior | Not claimed | Verify configuration UI, permissions, logs, rotation, and revocation |
| Chat, issue tracker, CI/CD, MCP, or Kubernetes integrations | Not claimed | Require current official documentation and reproducible evidence |
Integration acceptance
Test the failure path before rollout.
- 01Scope credentials
Use a non-sensitive repository and the minimum permissions needed for the test.
- 02Trace traffic
Record Git, model, package, update, DNS, preview, logging, and telemetry destinations.
- 03Revoke access
Expire credentials and confirm tasks fail safely without leaking secrets.
- 04Document support
Store release, provider, auth method, configuration, result, owner, and retest date.
Common questions
Integrations, answered.
Related: which Git providers?, supported models, data routes.
What does MonkeyCode integrate with?
MonkeyCode workflows require repository access, AI model access, development infrastructure, and supporting network services. The public README names GLM, Kimi, MiniMax, Qwen, and DeepSeek model families; exact Git providers, authentication methods, and versions must be verified.
Which Git providers does MonkeyCode support?
Public materials do not establish a complete provider-by-provider matrix. Confirm your specific provider and authentication method in a test with least-privilege credentials before connecting sensitive repositories.
Which AI models can I connect?
The current README lists GLM, Kimi, MiniMax, Qwen, and DeepSeek. Verify the exact model IDs, endpoints, regions, quotas, and provider terms available in your release.
Does MonkeyCode support MCP, CI/CD, or Kubernetes integrations?
These are not claimed on this page. Treat any such integration as unverified until you find current official documentation and reproduce it in your own environment.
How should I verify an integration?
Scope credentials on a non-sensitive repository, trace every outbound destination, revoke access to confirm tasks fail safely without leaking secrets, and record the release, provider, auth method, and result.
PRIMARY SOURCES