bug: Removed the github MCP server and slack MCP server from mcp.json so users can just use Loki without any other setup and add more later

README.md

@@ -164,21 +164,6 @@ guide you through the process when you first attempt to access the vault. So, to
 loki --list-secrets
 ```
 
-### First Time Setup
-In order for Loki to function correctly, you'll need to add a few secrets to the Loki vault so the MCP servers can
-function.
-
-**GitHub MCP Server:**
-* `GITHUB_PERSONAL_ACCESS_TOKEN` - A GitHub Personal Access Token with `repo` and `workflow` scopes.
-  See [Creating a GitHub Personal Access Token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens)
-
-#### Add the secrets to the Loki vault
-You can add the secrets to the Loki vault using the following commands (First time use will prompt you to create a vault 
-password file):
-```sh
-loki --add-secret GITHUB_PERSONAL_ACCESS_TOKEN
-```
-
 ### Tab-Completions
 You can also enable tab completions to make using Loki easier. To do so, add the following to your shell profile:
 ```shell
@@ -273,4 +258,4 @@ The appearance of Loki can be modified using the following settings:
 | `save_shell_history` | `true`        | Enables or disables REPL command history                                                                         |
 
 ## Creator
-* [Alex Clarke](https://github.com/Dark-Alex-17)
+* [Alex Clarke](https://github.com/Dark-Alex-17)

assets/functions/mcp.json

@@ -1,31 +1,8 @@
 {
   "mcpServers": {
-    "github": {
-      "command": "docker",
-      "args": [
-        "run",
-        "-i",
-        "--rm",
-        "-e",
-        "GITHUB_PERSONAL_ACCESS_TOKEN",
-        "ghcr.io/github/github-mcp-server"
-      ],
-      "env": {
-        "GITHUB_PERSONAL_ACCESS_TOKEN": "{{GITHUB_PERSONAL_ACCESS_TOKEN}}"
-      }
-    },
     "docker": {
       "command": "uvx",
       "args": ["mcp-server-docker"]
-    },
-    "slack": {
-      "command": "npx",
-      "args": ["-y", "slack-mcp-server@latest", "--transport", "stdio"],
-      "env": {
-        "SLACK_MCP_XOXC_TOKEN": "{{SLACK_MCP_XOXC_TOKEN}}",
-        "SLACK_MCP_XOXD_TOKEN": "{{SLACK_MCP_XOXD_TOKEN}}",
-        "SLACK_MCP_ADD_MESSAGE_TOOL": true
-      }
     }
   }
 }

docs/AICHAT-MIGRATION.md

@@ -3,8 +3,8 @@ Loki originally started as a fork of AIChat but has since evolved into its own s
 
 As a result, there's some changes you'll need to make to your AIChat configuration to be able to use Loki.
 
-Be sure you've followed the [first-time setup steps](../README.md#first-time-setup) so that the Loki configuration 
+Be sure you've run `loki` at least once so that the Loki configuration directory and subdirectories exist and is
-directory and subdirectories exist and is populated with the built-in defaults.
+populated with the built-in defaults.
 
 ## Global Configuration File
 You should be able to copy/paste your AIChat configuration file into your Loki configuration directory. Since the 
@@ -208,4 +208,4 @@ Here's how to migrate your functions over to Loki from the `llm-functions` repos
   ```
   
 Refer to the [custom bash tools docs](./function-calling/CUSTOM-BASH-TOOLS.md) to learn how to compile and test bash 
-tools in Loki without needing to use `argc`.
+tools in Loki without needing to use `argc`.