App Settings

Configure Memex's core functionality, integrations, and system behavior.

Overview

App Settings control Memex's system-level behavior and integrations. Unlike Agent Settings which affect how the AI behaves during conversations, App Settings configure the underlying platform capabilities and external connections.

Access App Settings through the main Settings menu in Memex. These settings apply across all projects and conversations.

MCP (Model Context Protocol) Support

The Model Context Protocol (MCP) has quickly become a standard in AI, acting like a universal "USB-C port" that connects AI models to tools, data sources, and services. MCP eliminates the need for fragmented, custom integrations by providing a standardized way for AI to interact with the digital world.

What Makes Memex Different

Memex is unique because you can both build and use MCP servers. Memex can even code an MCP server, then add it to its own context, test it, and iteratively debug and improve it—all autonomously.

Using MCP Servers

MCP extends Memex like an infinitely expanding toolset. You can customize the tools Memex has access to for a tailored experience matching your specific use case.

Accessing MCP Management:

  1. Go to Settings (⚙️) → MCP tab

  2. Manage existing servers or discover new ones

  3. Configure server-specific settings

Three main sections:

  1. Configured Servers

View and manage your currently installed MCP servers:

  • See all available MCPs with their status (enabled/disabled)

  • Toggle servers on/off without uninstalling

  • Manage individual tools within each server

  • Monitor server health and connection status

  1. Server Directory

Browse and install curated MCP servers with one-click installation:

  • Neon: Database management and querying

  • Netlify: Web hosting and deployment

  • GitHub: Repository management and code operations

  • Context7: Documentation and knowledge base access

  • Browser Automation: Web scraping and interaction

  • And more: Growing directory of tested, Memex-optimized servers

The Server Directory focuses on MCPs that are tested with Memex and help with the most common development tasks.

  1. Add Custom Server

Install any MCP server from the broader ecosystem:

  • Install from GitHub repositories

  • Use local development servers

  • Configure custom server parameters

  • Set up authentication and credentials

Installing a custom MCP server:

Server Name: my-custom-server
Command: npx -y @my-org/my-mcp-server
Arguments: --config /path/to/config.json
Environment Variables: API_KEY=your_key_here

Working with MCP Servers

Memex integrates with MCP servers intuitively—often requiring no special instructions. Simply enable the MCP server, and Memex understands how to use its capabilities.

Natural Integration Examples:

Browser automation:

Use playwright to check if this website is loading correctly and take a screenshot.

Documentation lookup:

Use context7 to look up the latest React documentation for useEffect hooks.

Database operations:

Use the Neon MCP to create a new table for user profiles in our database.

Deployment:

Use Netlify to deploy this React app and give me the live URL.

Building MCP Servers

One of Memex's unique capabilities is building MCP servers from natural language descriptions.

Example workflow:

I need an MCP server that can interact with the Stripe API for payment processing. It should handle creating customers, processing payments, and retrieving transaction history.

Memex will:

  1. Design the MCP server architecture

  2. Implement the Stripe integration code

  3. Create proper MCP protocol handlers

  4. Test the server functionality

  5. Add it to your available MCPs

  6. Help you use it in your projects

Benefits of building custom MCPs:

  • Tailored functionality: Exactly what your project needs

  • Reusable tools: Use across multiple projects

  • Team sharing: Share custom MCPs with your team

  • Ecosystem contribution: Publish useful MCPs for others

MCP Best Practices

Server Management:

  • Only enable MCPs you're actively using to reduce context overhead

  • Test new MCPs in non-critical projects first

  • Keep servers updated for security and functionality

  • Document custom server configurations

Performance Optimization:

  • Disable unused tools within servers

  • Monitor server response times

  • Use appropriate servers for specific tasks

  • Consider server location and latency

Security Considerations:

  • Review permissions before enabling servers

  • Use secure credential storage (see Secrets section)

  • Audit server access to sensitive resources

  • Regularly review enabled servers and their permissions

Secrets Management

Secrets are sensitive pieces of information like API keys, database passwords, or access tokens that applications need to interact with external services or protect data. Managing these securely is crucial to prevent unauthorized access and protect your accounts and data.

Memex provides a built-in secrets management system to help you store and use this sensitive information securely without hardcoding it directly into your project files or chat messages.

How Secrets Work in Memex

Secure Storage: Memex uses your operating system's native keychain (macOS Keychain, Windows Credential Manager) to store secret values. Memex itself never stores your raw secret values in its own files.

Local Access: Secrets remain on your machine and are only accessed when needed by processes initiated by Memex on your behalf.

Key Tracking: Memex maintains a list of secret names (keys) you've stored, but the actual values are encrypted and managed by your system's secure storage.

Managing Secrets

Adding New Secrets:

  1. Go to Settings → Secrets tab

  2. Enter a descriptive key name (e.g., OPENAI_API_KEY, DATABASE_PASSWORD)

  3. Enter the secret value

  4. Toggle visibility as needed while entering

  5. Click "Add Secret"

Updating Secrets:

  1. Click the Edit icon (✏️) next to the secret key

  2. Enter the new secret value

  3. Click "Update"

Using Secrets in Conversations: Reference secrets by their key name:

Use the API key stored as 'STRIPE_API_KEY' in Secrets to configure the payment gateway.
Connect to the database using the credentials in 'DATABASE_URL'.

Security Features

Case Insensitivity: Memex attempts to find secrets using various case combinations, so OPENAI_API_KEY, openai_api_key, and OpenAI_API_Key all work.

Permission Prompts: The first time Memex accesses a secret, your system may ask for permission. You can choose to:

  • Allow once

  • Allow always for Memex

  • Deny access

No Exposure: Secrets are never displayed in conversation logs or technical outputs—only referenced by their key names.

Legacy Migration

If you have secrets stored in Memex's older format:

  1. You'll see a migration banner in the Secrets tab

  2. Click "Migrate Secrets"

  3. Review migration results and fix any issues

  4. Old format secrets are converted to the new secure system

Other App Settings

Privacy Mode

Your code is never stored anywhere other than your machine.

If you enable Privacy Mode, your conversations are also never stored anywhere other than your machine. Otherwise, we may collect usage and telemetry data (including prompts, code snippets, or app activities) to help improve Memex.

Privacy Mode is available to Build and Scale users, and can be managed from the Settings -> Other page.

Sound Settings

Toggle if you'd like a sound notification to play when the Memex agent finishes a task.

PreviousAgent SettingsNextTeam Management

Last updated

Was this helpful?