Sign-in and security
How sign-in works
Section titled “How sign-in works”Your app connects with OAuth, the standard sign-in method for MCP servers. When you connect, the Teleflows MCP server opens a sign-in page in your browser. You paste your Teleflows API key there, not into the app.
The server checks the key with Teleflows before it accepts it. After sign-in, you return to your app.
Where your key is kept
Section titled “Where your key is kept”- The key is stored encrypted on the Teleflows MCP server.
- It is used only to read data for you, within what its role allows.
- The assistant never sees the key.
- A connection lasts up to 90 days. After that, you sign in again.
Read-only
Section titled “Read-only”The server is read-only. Nothing in Teleflows can be created, changed or deleted through it. Requests to change something are refused.
Check the sign-in page
Section titled “Check the sign-in page”Before you paste your key, check what the sign-in page shows:
- The app. It names the app you are connecting, and the website that identifies it, for example ChatGPT (identified by chatgpt.com).
- The return address. After you connect, you are sent to this address, for example claude.ai or chatgpt.com.
- Unverified apps. An app marked unverified app chose its own name. Continue only if you started the connection yourself and recognise the address.
A sign-in must be finished within 10 minutes, in the browser window that started it. After 5 wrong keys, the sign-in stops and you start again from your app.
Stop access
Section titled “Stop access”See Revoke access.