Choose the correct guide
After signing in, use the client cards in Connections to check available setup paths and requirements. These include development tools such as Codex, Cursor and VS Code. A listed card does not mean every client version and plan supports every feature. Read any availability or unverified-connection notes.
Step by step
- Check that weclapp is connected.
- Select your Live or Demo system in Connections.
- Choose the exact client you use. Apply the displayed configuration in that client's designated settings.
- Complete sign-in and the consent screen using your own account.
- Start a new session and ask for a read-only connection and identity check.
Do not copy a configuration from another workspace. A weclapp API token is not a substitute for the required MCP sign-in.
If you installed a plugin
A plugin may include skills and a connection together. First check what is actually installed and signed in. Avoid duplicate entries for the same access. Do not remove a working connection as a precaution.
If sign-in is unavailable
Read your client card and its linked vendor guide. Some organization accounts require administrator approval. Do not change the transport protocol or system URL based on a guess.
Continue with first questions, skills or troubleshooting.