Least privilege
Every connection starts read-only and gets one specific write permission at a time, each with a reason.
MCP workshop
With the Model Context Protocol a coding agent can read your tickets, look things up in your documentation and test the app in a browser. Each connection is also a new way for something to go wrong. This session is about choosing the useful ones and setting the rules before anything is connected.
Free 15-minute call with our team, or call +49 761 519 751 50 (24/7, English + German)
The Model Context Protocol, MCP for short, is an open standard for connecting AI agents to external systems. A server exposes a set of tools, for example reading a ticket or opening a page, and the agent decides during a task when to call them. Claude Code, Codex and Cursor can all work with MCP servers.
Without such connections people act as the agent's clipboard: they copy the ticket text into the prompt and paste the error message back. With them the agent fetches what it needs. That saves time and hands the team a decision: what the agent may reach, with which rights, and who checks what it did there.
| Connection | What the agent uses it for | Rights to start with |
|---|---|---|
| Issue tracker | Reading the ticket it works on, linking the pull request | Read, plus comments |
| Documentation | Looking up conventions and library documentation | Read-only |
| Browser testing | Opening the app at a phone-sized viewport, clicking through a flow, reading console errors | Staging or preview address only |
| Repository host | Reading pull requests and review comments | No merge and no admin rights |
| Error tracking | Reading the stack trace that belongs to a bug report | Read-only |
Every connection starts read-only and gets one specific write permission at a time, each with a reason.
The agent uses its own narrowly scoped tokens, never a developer's personal login. They can be revoked without locking a person out.
A ticket or a web page can contain text that reads like an instruction. The agent has to treat it as data.
Comments, status changes and anything visible to others pass a human check until the team trusts the setup.
From ticket to deployed build: which tools are involved, and where do people copy information by hand today?
Start with the ones that save the most copying and need only read rights.
Configure the servers, check which tools they expose and what the agent can see through them.
For example: take a ticket, fix it, open the preview at a phone viewport and report what you see. The group watches which calls the agent makes.
The safety rules go into the project memory file and into the team's security documentation.
Two working connections, a written rule set, a list of the connected servers with their rights and owners, and a shared view of what stays off limits. For WebViewGold itself there is nothing to install: its documentation is published in a machine-readable form that agents read directly, see the docs for coding agents.
We bring an MCP playbook and secure workflows aligned with ISO 27001. Which of your tools are worth connecting is something to go through in a free call.
That depends on your tools, which is why the session starts with your release path. As a rule, prefer servers provided by the vendor of the tool or servers whose code your team has reviewed.
It is as safe as the rights you grant. Read-only access with narrow tokens carries little risk; write access to production systems deserves the same care as handing it to a new colleague.
No. Agents are useful with just a repository and a terminal. MCP pays off when people spend noticeable time copying information between tools and prompts.
Same result, different amount of work on your side. All three come with the approval guarantee and 24/7 human support.
$109 per platform, one-time
The WebViewGold license: a finished Xcode or Android Studio project. Paste your URL, set name and icon, switch on features, build and submit. Free updates forever.
See plans on the main page$349 per license, one-time add-on
No Mac, no Xcode, no Android Studio: configure in the browser, we build both apps in the cloud and hand them to App Store Connect and the Play Console.
How the Cloud Builder works Try the free demo$698 per platform $798
Send us your URL and icon. Our team configures, builds and delivers your app within 72 hours, white-label, with source projects. Both platforms for $1,158.
Full Service details Powered byWinter Sale prices valid until December 31, 2026.
Free 15-minute call: your app, your tools, your next step
Rather start right away? See plans and pricing or hand it over with Full Service.