Home / Docs / Cline and Roo Code

Connect Cline or Roo Code through one OpenAI-compatible endpoint.

Both extensions expose the same core fields: OpenAI Compatible, Base URL, API Key and Model ID. Validate the API first, then enter only models visible to your account.

ProviderOpenAI Compatible
Base URL/v1 required
Model IDcopy from /models
Roo Codenative tools required

Fields confirmed in the official docs

FieldClineRoo CodeMonkeyAI value
API ProviderOpenAI CompatibleOpenAI CompatibleSelect exactly this provider type
Base URLRequiredRequiredhttps://monkeytheme.com/v1
API KeyRequiredRequiredYour MonkeyAI key
Model / Model IDChoose or enter IDChoose a modelCopy an ID returned by /v1/models

Sources: Cline OpenAI Compatible documentation and Roo Code OpenAI Compatible documentation.

Validate outside the extension first

curl https://monkeytheme.com/v1/models \
  -H "Authorization: Bearer ***"

A valid key should return the models visible to that account. Without a key, production currently returns JSON 401 API_KEY_REQUIRED. A fake key returns 401 INVALID_API_KEY. This proves authentication behavior, not a successful model call.

  1. Copy a Model ID from the real response.
  2. Open the extension settings with the gear icon.
  3. Select OpenAI Compatible.
  4. Enter the Base URL, API Key and exact Model ID.
  5. Start with a small request before enabling automated actions.

Cline setup

API ProviderOpenAI Compatible
Base URLhttps://monkeytheme.com/v1
API KeyYour MonkeyAI API key
ModelExact ID returned by your account

Cline’s official page also exposes advanced model configuration. Leave those values at defaults until the basic request works; changing context, token and capability flags does not repair an invalid key or URL.

Roo Code setup and the tool-calling boundary

API ProviderOpenAI Compatible
Base URLhttps://monkeytheme.com/v1
API KeyYour MonkeyAI API key
ModelExact visible Model ID with native tool support
Roo Code’s current official documentation says it uses native tool calling exclusively and has no XML fallback. A successful /v1/models request does not by itself prove that a selected model supports native tools.

Diagnose by symptom

SymptomLikely layerNext check
401 JSONAuthenticationReplace the cached key and retest /v1/models
404 HTMLBase URLUse https://monkeytheme.com/v1
model not foundModel ID or account visibilityCopy the ID from the live model list
Direct API works, extension failsExtension stateCheck duplicate /v1, old key and selected provider
Roo cannot execute toolsModel capabilityConfirm native OpenAI-compatible tool calling

FAQ

Can Cline use MonkeyAI?

Yes. Cline officially supports an OpenAI Compatible provider with Base URL, API Key and Model ID fields. Use https://monkeytheme.com/v1 and a model returned to your account by /v1/models.

Can Roo Code use MonkeyAI?

Roo Code has the same OpenAI Compatible fields. Its official documentation also requires the selected model to support OpenAI-compatible native tool calling.

Why does /v1/models work while the extension fails?

The route and key may be valid while the extension still has an old key, duplicate /v1, an unavailable Model ID or a model without the tool behavior required by that client.

Does a 401 prove the provider is configured correctly?

A JSON 401 from /v1/models proves the API route exists but authentication failed. It does not prove the key, model or tool calling works.

Related guides

API Key troubleshooting

Separate 401, 404 and model errors first.

Open guide

Base URL /v1

Understand missing and duplicated API paths.

Open /v1 guide

Agent clients

Compare additional supported tools.

Open center